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
Some SQL commands can produce an infinite loop iterating the result set.
Ive tracked this down to them producing either unsupported protobuf types (eg. type 1)
or 0 columns (may be related).
The 0 column problem results in the iterator code to not advance the CSV pointer -- e.g the conditions never call the appropreate methods to read more from the CSV file if there are ' 0 columns' (triggered likely by the former issue) .
Examples to try
SHOW TABLES
MSCK REPAIR TABLE tablename
The text was updated successfully, but these errors were encountered:
Thank you, good catch. Would you like to take a stab at fixing it? You've already identified the source of the CSV parsing issue. I think you can duplicate this test
Some SQL commands can produce an infinite loop iterating the result set.
Ive tracked this down to them producing either unsupported protobuf types (eg. type 1)
or 0 columns (may be related).
The 0 column problem results in the iterator code to not advance the CSV pointer -- e.g the conditions never call the appropreate methods to read more from the CSV file if there are ' 0 columns' (triggered likely by the former issue) .
Examples to try
SHOW TABLES
MSCK REPAIR TABLE tablename
The text was updated successfully, but these errors were encountered: