-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingest of CSV (without header row) fails because of database column size limit #2626
Comments
It appears that the CSV file has no header. Indeed at least one column contains long text; treating that as a header is bound to fail. This is not to say that real headers will always have names that don't exceed 255 characters.
|
I think it is reasonable to require a header, as otherwise, there is no reliable way to tell. |
@oscardssmith I believe that during sprint planning @djbrooke ask you to do something this this issue. Combine it with #3767 maybe? I forget. |
Yeah, 3767 fix addresses this |
@oscardssmith ah, and you've already added the "connects to" line to pull request #3930. Perfect. Thanks. Closing. |
I noticed a red triangle and exclamation point in our test environment. When hovering over it, it says that the ingest succeeded, but failed to put the data in the database.
The logs show that the root cause is a 255 character limit on a column. I don't expect that values in a CSV file are always at most 255 characters, so this limit should be removed.
(Perhaps not relevant to this issue, but recurring messages in the logs are related to Weld as included below.)
The text was updated successfully, but these errors were encountered: