-
Notifications
You must be signed in to change notification settings - Fork 30
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
Parsing trouble when a column is called "vector" #483
Comments
We probably also need to test for other similar cases like if the table name is also same as the cql data type like below:
|
Agreed @msmygit . My guess is that I got something in the CQL parser code, specifically we're trying to pull out some kind of non-keyword token and failing miserably. Any fix to this ticket should involve a test to validate that we've addressed the issue generally. |
I have checked with
|
In the meantime @phact has brilliantly found a workaround:
|
I got the same above issue with the vector column named as vector. Some of our libraries names the vector column as such, so that makes it imp to address this issue. |
Adding details for the |
On a schema like this
it happens that
dsbulk unload
gets confused byvector
and the unload operation fails with something likev1.11
The text was updated successfully, but these errors were encountered: