-
Notifications
You must be signed in to change notification settings - Fork 310
Cannot resolve table name since 3.4.2 #1293
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
Comments
We changed the naming behavior for user-provided identifiers. If you provide a table name, then we use the exact lettercasing and let Cassandra's driver's The fix is to use lowercase names in |
By converting the name to lowercase, it has indeed fixed the issue. Are there any plans to create a plugin that will scan the whole module and change the annotation values to lowercase? As of now, my company has hundreds of entities across multiple modules and it would be a tedious task to do the conversion. |
Apologies for the inconvenience, we weren't aware that this change has such a wide negative impact. You could post-process entities and tables programmatically and set lowercase CQL identifiers via |
Issue
We recently upgraded a module of ours to
spring-data-cassandra 3.4.2
and our service is not able to identify any of the Cassandra tables when we are doing a query.For example, when we try to insert a new entry to a table, we get the following exception:
Full stacktrace:
https://gist.github.com/mackatozis/33f4dfae804d25b9f0f819ac575af34e
If we force our module to use
spring-data-cassandra 3.4.1
everything works as expected.Steps to reproduce
I have created a small demo that reproduces the issue:
https://github.com/mackatozis/cassandra-demo
The text was updated successfully, but these errors were encountered: