I just had a go at getting index support for edges. It largely follows the approach taken for vertex indices.
There's also a small fix in OrientGraph.java for a potential ClassCastException being thrown during index lookup when using a remote connection. This has the exact same exception message as in the old issue #71 and seems to happen when using a remote connection and a NOTUNIQUE index.
Coverage increased (+3.1%) to 84.257% when pulling 91ab9a32b1103521c8883df9dab72fce31d7c3c7 on johnrevill:master into 73cbc5ad16015b77d2daa094a79410bbc891a76f on mpollmeier:master.
Coverage increased (+3.3%) to 84.455% when pulling cf70835152aaf995386422053517a9b7b1e6f555 on johnrevill:master into 73cbc5ad16015b77d2daa094a79410bbc891a76f on mpollmeier:master.
Hi there,
I just had a go at getting index support for edges. It largely follows the approach taken for vertex indices.
There's also a small fix in OrientGraph.java for a potential ClassCastException being thrown during index lookup when using a remote connection. This has the exact same exception message as in the old issue #71 and seems to happen when using a remote connection and a NOTUNIQUE index.
Cheers, John