-
Notifications
You must be signed in to change notification settings - Fork 49
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
QL 0.8.3 can't insert values into existing table. #638
Comments
@StWiemann thanks for reporting this! It looks like it could be a backward compat issue introduced by #565. Can you confirm your table ( |
did you get the error while querying or doing inserts? in principle doing an insert should automatically add the column. if that's not the case, that's the problem here, and worst of all, this is not captured by the backward compatibility tests :/ |
the issue is during inserts. most probably in the crate version you created the table, the default policy for columns is "strict", and this makes it bomb can you try as temp fix to alter the table from cratedb? |
You are absolutely right. I was wondering what instanceid was refering to, but that is the problem. It is not there.
Yes, while isnerts. Thank you! I will give your fix a try right now and let you know. |
The ALTER TABLE command gives me a "ALTER OK, -1 rows affected (0.055 seconds)" response. QL still throwing the same error.
`Error! MapperParsingException[Mapping definition for [some_thing] has unsupported parameters: [fields : {keyword={type=keyword, ignore_above=256}}]]` Querying the column_policy like this: EDIT: Might this be a CrateDB-Bug? |
probably the table column_policy can't be changed :/
we will find a way to fix this issue, but meanwhile, i guess that's fastest patch possible |
This worked! Thank you! Still strange behaviour that the insert with Int worked, but doesn't with text 🤷 |
I had the same problem and the solution with |
Hi, |
hi @tstorek, we were thinking of implementing some sort of data migration tool, but haven't got around to doing it yet. @chicco785 opened #639 so we're able to at least reproduce, but as it turns out automated data migration will take some time---probably something we'll tackle in 2023. For the time being, the only solution I can offer you is to write yourself a SQL data migration script with one alter table statement for each table you have as suggested in this thread...so sorry for the inconvenience!! |
Hi, we saw this bug using Timescale DB as well. Are there any updates regarding solving this issue? |
Hi @Greenstreet123 :-) No unfortunately we haven't worked on this yet. The best solution I can offer at the moment is the one suggested above--i.e. manually run an alter table command to add the missing column. |
Hi, thanks for quick reply. |
We sketched out a solution involving a data migration tool that could be used in the future too for similar scenarios. It could be similar to what we already do with Timescale: where the init container lets you run SQL scripts on start-up. But yes, we've had no time to go past the idea phase and come up with an implementation plan. |
``I just tried to upgrade to QL 0.8.3 because of the new authentication-feature.
Despite turning off caching and authentication I do get an error which is not present with QL 0.8.2 and the same config despite the version.
Orion:3.5.1
QL:0.8.3
CrateDB:4.6.7
Everything running in Kubernetes.
Config QL:
I have to admit that this is not much to go by, but maybe you guys recognize the fault. I didn't test it with a "fresh table", since I'd really would like to keep the existing ones. But if it helps you I could try to simulate some fresh data on monday.
I didn't really find anything helpful on these errors:
crate.client.exceptions.ProgrammingError: ColumnUnknownException[Column instanceid unknown]
crate.client.exceptions.ProgrammingError: MapperParsingException[Mapping definition for [type] has unsupported parameters: [fields : {keyword={type=keyword, ignore_above=256}}]]
Very verbose log-message starting from message before the ERROR-message:
The text was updated successfully, but these errors were encountered: