You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you run large CSV import jobs in parallel sometimes the error "CSV lines(s) must not be null" is thrown. When you run the jobs sequentially it does not happen.
To Reproduce
Steps to reproduce the behavior:
Create 2 tables in Opal (only the dictionary)
Import CSV files larger than 10000 rows
Import a second CSV file larger than 10000 rows
A "CSV lines(s) must not be null" error is thrown
Expected behavior
The import jobs successfully imports the data.
Screenshots
NA
Desktop (please complete the following information):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
When you run large CSV import jobs in parallel sometimes the error "CSV lines(s) must not be null" is thrown. When you run the jobs sequentially it does not happen.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The import jobs successfully imports the data.
Screenshots
NA
Desktop (please complete the following information):
Additional context
Check the attachment logfile: opal-csv-null-lines.log
The text was updated successfully, but these errors were encountered: