luigidellaquila
commented
5 years ago HI @anukul-mohil
The problem here is that your DB contains a broken edge: #89:7648{out:null,in:#45:2}
What I can suggest is to run a DELETE EDGE #89:7648 from Studio.
If it fails, you can manually check record #45:2 (from Studio) and see if it points to the edge, detach it manually using plain SQL and delete the edge with DELETE #89:7648 UNSAFE
It would be interesting to understand how it happened, but I don't know how easy it is. What I can suggest in general is to upgrade to v 3.0.9, as it contains a lot of bug fixes
Thanks
Luigi
anukul-mohil
OrientDB Version: 3.0.4
Java Version: "1.8.0_131"
OS: CentOS 7.3
Expected behavior
Return all the vertices having an edge to the vertex with name 'main',
g.V().has('MyVertex', 'name', 'main').in()Actual behavior
Returns Error:
java.lang.NullPointerException: out vertex on edge COMPONENT_OF#89:7648{out:null,in:#45:2} v2on studio and in server logs this:Steps to reproduce
We can't seem to reproduce this but there were some rollback transactions that failed, that may have caused this. We tried running
repair databasecommand which did return thisThe only thing it did was in the exception returned one of the vertex which was deleted but was showing up like this:
that is I think it just cleared the dead vertices lying around but apparently was not able to clear the reference of the dead edge on this
mainvertex.Any help is appreciated. Thanks.