Hi,
We are using the 1.7.9-SNAPSHOT version through remote access. In our
application, all edges are created by the Graph API funcions. The code that
creates the edges are like this:
ODocument citationDoc = elementIdCache.get(citationId) ;
if (citationDoc == null)
throw new NdexException ("Citation Id:" + citationId +
" was not found in elementIdCache.");
OrientVertex citationV = graph.getVertex(citationDoc);
edgeVertex.addEdge("eCitation", citationV);
We didn't see any error or warning when loading data into the db, but we
found the database was corrupted after the loading. We get different result
when we query the same data from different directions. For example
orientdb {db=ndex}> select count(*) from (traverse in_eCitation from #21:6)
where @class='edge';
----+-----+-----
# |@RID |count
----+-----+-----
0 |#-2:0|91
----+-----+-----
1 item(s) found. Query executed in 0.042 sec(s).
orientdb {db=ndex}> select count(*) from edge where out_eCitation=#21:6 ;
----+-----+-----
# |@RID |count
----+-----+-----
0 |#-2:0|94
----+-----+-----
1 item(s) found. Query executed in 0.795 sec(s).
>From one direction we got 91 edges, but from the other direction we got 94
edges. I tried our code to load the same data multiple times with empty
databases, and the error seems to be consistent.
I also tried the same application through 'plocal' connection and it seemed
to be working fine. I suspect this problem might relate to issue #2793 as
well?
Thanks,
Jing
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
