Hi everyone, I would like to start a discussion about JanusGraph 0.6.0 release. There were multiple requests from the community about ETA of 0.6.0 release. I wanted to check if there are any features

Hi Marc I've submitted this as a bug https://github.com/JanusGraph/janusgraph/issues/2515 Thanks

This discussion also plays on: https://lists.lfaidata.foundation/g/janusgraph-users/topic/multiple_vertices_generated/81197948

This discussion also plays on: https://lists.lfaidata.foundation/g/janusgraph-users/topic/performance_issue_large/81197952?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,81197952

Hi JG community 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

Hi @simone We were planning to segregate the static configurations from the runtime dynamic configurations (last update TS from client, etc.). AFAIK only the static configurations are required by the

HI @sauverma, nice, we are truncating the table, too. It's good to have your confirmation that it could safely workaround the issue. We will analyze the `gc_grace_seconds` setting now. Just for

In scylla grafana board, this issue is seen with high number of foreground read tasks.

Thank you folks for getting back. @Simone3, yes this issue comes out as read timeout from the shard holding the system_properties table (there is only 1 partition for system_properties

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

Hi Saurabh, we are experiencing the exact same issue: spark job with one janusgraph instance per partition calling a scylladb cluster. Our symptom is a ton of timeout exceptions due to missing QUORUM

Hi Saurabh! Thanks for reporting that issue! Looking at the open pull requests, I don't see one that addresses this problem. You're always welcome to share your solutions by discussing them here or

Hi all - The interaction with the underlying KV store via janusgraph client hits the `system_properties` table with a range query where the key is `configuration` (key = 0x636f6e66696775726174696f6e)

Ahh. Actually think I may have answered my own question building from source. Looks like hadoop:2.7.7 and spark-gremlin:3.4.10 are still using netty 3 and the POM just bumped to the latest netty 3

Noticed that there are two versions of Netty in the POM for JanusGraph: - version 3:https://github.com/JanusGraph/janusgraph/blob/master/pom.xml#L806 & - version 4:

Hello, I'm working on planning another JanusGraph community meetup and wanted to gauge community interest in doing an in-depth focus on tackling OLAP/graph algorithmic work with JanusGraph. This has

Sounds like a good thing to do. We should consider updating our documentation (#54) before that, so that users who get started with the new release don't experience any issues regarding installation

Hi all, I think we should consider doing a release of the janusgraph-foundationdb adapter sometime soon. There have been several changes since the initial 0.1.0 release that warrant a new release.

I also now find groups.io to be not as good experience as Google Groups. 1) As noted by Marc, there is no way to see on UI that there are threads with new messages you didn't see. Here is the issue

Hi Marc, > 1. After a new reply appears to a thread, the thread still appears as "read" in the web ui. In other words, you have to open every thread to see whether new replies are present. That's