Hi, I have JanusGraph with Scylla and Elasticsearch in a docker. I'm connecting to JanusGraph on backend using gremlin. I see this error only on my server and not on my local machine. What does it

Hi Roy, Nice to see you back here, still going strong! I guess the TraversalVertexProgram used for OLAP traversals is not well suited to your use case. You must realize that 200 stages in an OLAP

The graph has 100 million vertices and 100 edges Graph data is saved at HBase Table: MyHBaseTable. The size of MyHBaseTable is 16.2GB: root@~$ hdfs dfs -du -h /apps/hbase/data/data/default/ 16.2 G

Thanks Evgenii

Hi Peter, This seems more relevant: https://docs.janusgraph.org/basics/configured-graph-factory/#graph-and-traversal-bindings So, some JanusGraph and GraphTraversalSource objects are created remotely

Hi! I am trying write select-query and my perfomance is very slow when I call method toList(). How I can improve this perfomace ? My example: long start; long end; try

Hi Peter, Have you tried the suggestions from an earlier thread: https://groups.google.com/g/janusgraph-users/c/w2_qMchATnw/m/zoMSlMO5BwAJ Best wishes, Marc Op woensdag 30 december 2020 om

Hi Zach, If you want to run the query in a multi-threading manner, try enabling “query.batch” (ref: https://docs.janusgraph.org/basics/configuration-reference/#query). Since you are using

Hi Marc, Boxuan, Thank you for the discussion. I have been experimenting withdifferent queries including your id() suggesting Marc. Along Boxuan’s feedback, the where() stepperforms about the same

Dear All, I have installed/configured a single node JanusGraph Server with a Berkeley database backend and ConfigurationManagementGraph support so that I can create/manage multiple graphs on the

Hi Marc, I think it will be as same slow as the initial one if not even slower. If I recall correctly, JanusGraph always fetches the whole edge (column + value) even if you only need the count (in

Hi Zach, Boxuan, There is one thing I do not understand. According to the JanusGraph datamodel, the outE relatationIdentifiers are stored in the vertex. So, retrieving all outE() relationIdentifiers

Hi Zach, I have some concerns over concurrency and consistency issues, but this might still be a nice feature to have. I think you could open a new discussion on

Thank you Boxuan, Was using the term “job” pretty loosely. Your inference about doing these things within ingest/deletion process makes sense. I know there is a lot on the community’s plate

Hi Zach, Personally I think your workaround is the most optimal one. JanusGraph does not store number of edges as metadata in the vertex (there are both Pros & Cons for doing / not doing this). Btw do

Hello all, Curious about best approaches/practices for scalabledegree-centrality search filters on large (millions to billions of nodes) JanusGraphs. i.e. something like : g.V()

Hi Boxuan! I perhaps wasn't clear. The composite indexing didn't solve the locking issue (it went away by itself 🙄, as if there's a cold start issue). However, my actual problem, about failing to

Actually I have around 70 fields. So my doubt is - whether is it possible to insert so data without bulk upload so that Janus graph will create it's own schema and letter for remaining data I will use

That's right

All these properties I need to set in the Janusgraph properties file right? I mean the config on which the server is starting. I mean the file where we set the backend storage and host etc.