My guess would be that it's because you have some kind of index that is being updated when you add those edges (note 'BackendTransaction.acquireIndexLock' in your call stack). I would see if you can

You can set the configuration property 'query-force-index' to true and JanusGraph will throw an exception instead of printing the

Great, congrats from me too! Marc Op woensdag 19 april 2017 20:26:16 UTC+2 schreef Collin Scangarella:

Cheers, congrats on the release. We'll be switching over shortly.

JanusGraph has 2 drivers for Cassandra, one using Astyanax ('cassandra') and using Thrift directly ('cassandrathrift'). The first release will continue this support, as we're looking for solid

Hi all, Question to cassandra module developers. I see that JanusGraph uses Astyanax for Cassandra 2. As there will be no Astyanax for Cassandra 3, have you decided on what to do? Are you going to

Hey, That worked perfectly. Thanks a lot!!!! Regards, Neelesh

The idea is that you shouldn't have to transfer any data, you can just configure JanusGraph flags to match the default values in Titan, such that it would just work in-place. Since Titan/JanusGraph

I am currently using Titan 1.0.0 with Cassandra backend and Elasticsearch for indexing. Our graph has 100 million nodes and 170 million edges with a replication factor of 2 and distributed across a

since we don't have the first release yet, I hope no one. lol We (where I work) are planing on switching from Titan to JanusGraph as soon as it gets released. We already moved some of our code to

Trying to write unit tests to determine whether indices are being used. The best indication I've seen is the log message: 15:56:00,517 WARN StandardJanusGraphTx:1273 - Query requires iterating over

Joe, thanks for reporting back with your solution. This sounds like a bug. I've opened up an issue to track it. https://github.com/JanusGraph/janusgraph/issues/220 -- Jason

Thanks for the help Marc. Turns out I set storage.hbase.short-cf-named to false in my code and didn't set that in the gremlin properties file. You have no idea how many days I've been

Thank you Marc. You raise a good point - I can access the graph fine from Java code using gremlin commands like: JanusGraphQuery query = graph.query.has("name", "test"); if

Hi Joseph, I am still on Titan/HBase, but the things should work the same. Code to connect: config = new

Hi Joseph, I am still on Titan/HBase, but the things should work the same. Code to connect: config = new

Thank you Marc. Yes, I've even tried very simple graphs of just a few vertices, commit, write out graphML, and then close. I can also load the graph from HBase, and export graphML OK. It

Hi Joseph, My first idea: did you commit the transactions that inserted the vertices and edges into JanusGrpah? Cheers, Marc Op dinsdag 18 april 2017 04:48:02 UTC+2 schreef Joseph Obernberger:

Sure, you can find it at: https://github.com/apache/tinkerpop/pull/534 https://issues.apache.org/jira/browse/TINKERPOP-1566 Cheers, Marc Op dinsdag 18 april 2017 04:21:19 UTC+2 schreef Jerry He:

I have a COMPOSITE index. It builds correctly, awaits completion as per JanusGraph Chapter 8 docs. All that is well. But I CANNOT USE THE INDEX. When I call getIndexStatus() on the index it reports