Open bblonski opened 7 years ago
Further investigation seems to indicate the issue occurs when records are removed from the database. The traversal still tries to iterate through missing vertices which causes the null pointers. I've tracked it back farther to OrientVertex:65. The call to .rawIterator() appears to return deleted vertices. Perhaps the call should be to .iterator() instead?
In addition to calling .iterator() as bblonski suggested, I added a filter to ignore any nulls while streaming over the collection. This appears to have fixed the issue we were having.
Hi @bblonski
Is this issue still valid? I checked the code but too many things have changed, so the patch from @ken-at-sri cannot be applied anymore
Thanks
Luigi
Ops, sorry, checked the wrong implementation (TinkerPop2), assigning to @maggiolo00 for a check
Thanks
Luigi
I have several times run into a NullPointerException on OrientEdge:48. The rawDocument comes back null and throws the NPE on rawDocument.getClassName(). I'm not sure what's causing the issue. Inspecting the database shows no issues and the queries will work for a time until suddenly they do not and will consistently throw NPEs until the database is reset.
Version is v3.2.3.0 against OrientDB server v2.2.10.