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
I think the arrow parser will throw an exception if the number of columns doesn't match:
e.g.
EXPECTED ERROR: Copy exception: Invalid: CSV parse error: Expected 3 columns, got 15: 0,Alice,1,true,false,35,5.0,1900-01-01,2011-08-20 11:25:30Z+00:00,3 years 2 days 13 hours 2 minu ...
I think the arrow parser will throw an exception if the number of columns doesn't match
but the table schema should be valid before - i wouldn't rely on the implementation detail of arrow here
especially when there were (if im correct) talks to remove the arrow dependency someday
We should throw an exception when the num of columns in files are not expected, i.e., not matched with the num of properties defined in table schema.
The text was updated successfully, but these errors were encountered: