Issue copied from:
I'm using orientdb-1.6.0-20131025.164813-147-distribution. When I run the distributed server the OrientBaseGraph.addVertex doesn't update the document id. So it'll be something like "#15:-3".
It looks like the issue is when calling graph.autoStartTransaction().
If I bypass addVertex and just create a new OrientVertex without properties and called save on it, it worked. If I did it with properties it didn't work. So I commented out the graph.autoStartTransaction(); in OrientElement.java setProperties method and it worked.
Right. I create an OGraphDataBase (or acquire from global) and pass that into a new Blueprints OrientGraph. Using this blueprints graph, I call addVertex. The id of the vertex that is returned doesn't have a document id just a cluster id (#15:-1). It also says that the vertex is not persisted and has an internal_status of NOT_LOADED. But it does save the vertex in the DB.
@lvca What is the status of this bug? This, essentially, kills our ability to deploy a distributed server configuration, which is disconcerting. Any chance of getting a hot fix for it?
Started looking into it. The cause could be the same as for: tinkerpop/blueprints#458
Have you already tried with OrientDB 1.6.3 ?
Any news on this?
We plan to today, will keep you posted.
This is still a problem on 1.6.3
I tried basic test cases and works. Can you provide me a test case to reproduce it?