We are facing a weird issue with Replication factor 3 with scylla DB as backend. - we are using index for looking up V in the graph - observation is that for many vertices with the same index value, m

Hi all We are using janusgraph at zeotap at humongous scale (~70B V and 50B E) backed by scylla. Right now I am facing an issue in janusgraph_ids table, wherein there are large partitions created in t

Hi Marc ==>------------------------------------------------------------------------------------------------ Vertex Label Name | Partitioned | Static | -------------------------------------------------

Hi The issue still persists, and the vertex metadata is still missing for some vertices, after enabling https://docs.janusgraph.org/advanced-topics/eventual-consistency/, has someone seen the same iss

Another really strange observation gremlin> g.V().has('id','131594d6a416666b401a9e48e54ebc8f22be75e2593c5d98e2d9ecfd719d5f29').has('type','email_sha256_lowercase').valueMap(true) ==>[dpts_678:[1595548

Hi Claire In our earlier attempts to work with JG OLAP, we hit the bottleneck / bounded by scylla virtual token ring count (it appears thats the unit of parallelism while bulk export) Can you please s

Hi Elliot At zeotap we ve taken the same route to enable olap consumers via apache spark. We presented it in the recent janusgraph meet-up at https://lists.lfaidata.foundation/g/janusgraph-users/topic

Hi I am getting the below exception while ingesting data to an existing graph Job aborted due to stage failure: Task 349 in stage 2.0 failed 10 times, most recent failure: Lost task 349.9 in stage 2.0