Hi Ivan, When I first read your question on March 6 I thought this one was not for me, but I see now that you still did not get an answer. I agree it looks suspicious, but there is still one thing I

These are all good suggestions. Not sure if it would be feasible to recreate your db, but if it was, you may be able to use edge TTLs:

I'm definitely not a Titan/Janus or ES expert so I'm not sure how it works. But I imagine if you had an index by label, timestamp, asc, then you would only ever hit the tip of the index

Hi, I have a Spark-based program, which writes vertices and edges to a JanusGraph cluster (Cassandra backend). Once the write is complete, I would like to execute an OLAP traversal for all vertices,

Hi Marc, Thanks for this. Yes it is a mixed index with elasticsearch as the backend. I've thought about the poor man's approach and I'm going to give that a try. In fact I can probably query

Thanks Robert, I will follow the path you have suggested and see what that I can achieve. The problem with the g.V() queries is that it is iterating over all vertices, so it is fast when I first

Hi Kevin, By an "elasticsearch index" you do mean a mixed index, don't you? Actually, indexing does not help you too much, because your query still hits 1/7 of your edgestore. The way to go here is to

I'm not sure I would use bothE(). Have you tried just outE()? I would be curious to see if it's querying that's slow or if it's dropping. Try using profile() or using time of count() instead of

Hi, I have been using Titan for a while and have recently moved to Janusgraph. Thanks for revitalising the project! I am using Janusgraph to look at social chat that is generating approximately 7

Hi Jerry, Thanks for your answer. I'll keep in the loop with this one. In the meantime, I'll stick to the old versions. Best, Gabriel.

This is the Issue that tracks it before the first release comes out. https://github.com/JanusGraph/janusgraph/issues/102 Thanks, Jerry

Can you provide more details on what is going wrong? It is a bit hard to debug your situation without any graph data. I tried this... $ ./bin/janusgraph.sh start Forking Cassandra... Running

Hi, I was previously using Titan and now I migrated my code to JanusGraph. I'm still using it with the latest Titan supported versions of the backends (as written here:

Hi, I'm using Gremlin Server in the JanusGraph package and trying to extract a subgraph. :> sg =

This is a two node cassandra cluster with Netwoktopology strategy. The data ownership is 100% on both the nodes. KEYSPACE my_ks; CREATE KEYSPACE my_ks WITH replication = {'class':

Thanks, this worked perfectly. The JanusGraphTransaction object also has a getVertices method which allows me to fetch them by ID. Performance seems pretty good on the small set of data I have, ill

It depends on your replication factor. If you didn't set it explicitly, the default RF=1. As you add nodes and the data gets distributed across the Cassandra nodes, the coordinator may need to connect

We are using Titan and Cassandra and will be moving to JanusGraph in the future. I am are observing that graph query performance degrades with increased latency between Cassandra nodes. We are using

Hi Samik, Thank you too for posting the solution. Marc Op dinsdag 7 maart 2017 04:37:32 UTC+1 schreef Samik R:

This was seemingly happening because I was running out of memory on the VM. I am consistently getting results after ensuring enough memory is available. Thanks. -Samik