-
Notifications
You must be signed in to change notification settings - Fork 24
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
Secondary index recreated even if it already exists #50
Comments
No, this is not expected and indexes should not be recreated. |
For briefness I've removed the getters/setters but they all follow the same pattern as follows
|
BTW, I have the system.log file from a period where the app started that shows the creation/initialization of the indexes. Problem is I don't know how to attach it to the issue, seems I can only attach images, not text files. If you would like a copy of the log, let me know, along with where I can send it, and I'll get it to you. |
I figured the issue: p.s. |
We are having trouble with the sync process in that we get a number of "schema not synchronized" messages on application startup. We are using the auto sync feature of this library and no tables have been changed nor have any secondary indexes been altered. What we see in the Cassandra log is that the tables don't change but each index is recreated and it is this change that appears to be causing our out of sync problem. Is this expected, and if it is, is there a way to turn it off so that it only happens if the index has been changed?
The following is an example of a class that is using annotations to describe the indexes:
The text was updated successfully, but these errors were encountered: