orientdb: Index Handling Regression in 3.1.x / Commercial Support Discontinued?
OrientDB Version: 3.1.3
Java Version: 1.8
OS: Linux
Expected behavior
The index should at all times be in sync with the graph and a index lookup should never return null when hasNext indicated that element are available.
Actual behavior
Index lookups via tx.getEdges return null values via Iterator#next() although it.hasNext() was previously true.
Steps to reproduce
A reproducer for the issue can be found here: https://github.com/gentics/orientdb-reproducers/blob/master/src/test/java/com/gentics/odb/IndexRegressionTest.java
I also posted details to a connected / similar issue in the commercial support system: https://www.prjhub.com/#/issues/10986
I have however not received feedback in a long time. Is the commercial professional support still operational? We noticed that the website was taken down and all links to documentation etc. are now broken: https://orientdb.com/ Emails are also rejected by the mailserver. We did not receive any update or heads-up about these changes. Is OrientDB going out of business?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (7 by maintainers)
Commits related to this issue
- Fix regression on index create + delete in the same tx Resolves #9402 — committed to orientechnologies/orientdb by luigidellaquila 4 years ago
- Fix management of index entries in tx with linked documents Resolves #9402 — committed to orientechnologies/orientdb by luigidellaquila 4 years ago
- Fix backward compatiblility issue with custom TinkerPop predicates Related to #9402 — committed to orientechnologies/orientdb by luigidellaquila 4 years ago
- Fix backward compatiblility issue with custom TinkerPop predicates Related to #9402 — committed to orientechnologies/orientdb by luigidellaquila 4 years ago
@luigidellaquila Thanks for the fix. I can confirm that it fixes the reported issue. We have however still failing tests which seem to be index related. It seems the reproducer was not able to catch all issues. I’m currently working on a reproducer which also reproduces another NPE which we are having with 3.1.3+Patch.