-
Notifications
You must be signed in to change notification settings - Fork 872
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
Index breaks after upgrade migration #10367
Comments
Hi, Thanks to report this, we will double check, do you have by any chances logs/stack traces related to this problem, it may speed up the resolution. Regards |
Yes. This is a breaking NOTUNIQUE index rebuild (it loops somewhere so I cut it at some point):
|
Hi, I think this is the case because of changed behavior, so now if you set "ignoreNullValues=true" if you save a record with a null value it does give an error, this was not the case before, I'm double checking this logic and when it was changed, because ignoring should not mean failing, but I guess the old storage maintainer didn't think so, will update soon on this. |
Hi, I actually found that there where two checks one high level to avoid to send null to low level, and one low level that create this issue, in the case of rebuild index the first high level check was missing, so I did add it, this should be fixed from the next hotfix 3.2.38. Regards |
OrientDB Version: 2.2.37 -> 3.2.36
Java Version: openjdk version "1.8.0_412"
OS: Macbook pro M3 using docker: linux/arm64/v8
Expected behavior
Rebuilding an index does not break the database
Actual behavior
When causing a rebuild after the import it break the database, making it impossible to log in over console or over the java library.
Steps to reproduce
Export a database which have a class with an index created using: "CREATE INDEX Idx ON Example (id) NOTUNIQUE METADATA {ignoreNullValues: true}" on orientdb 2.2.37 (ran directly on the host) and export using the console.
Import into orientdb3.2.36 (dockerized).
Log into the web interface and rebuild the index.
I could not fix the broken database.
Edit: I did not encounter this issue on "UNIQUE" indices.
Workaround
After importing the database, drop the index and create it again.
The old index had "SBTREE" engine and the new one has "CELL_BTREE" to which I can't seem to find documentation.
This is only possible if the database is not broken yet.
The text was updated successfully, but these errors were encountered: