When I look at https://github.com/JanusGraph/janusgraph/blob/ce79ec50e0c882c9ccc62e73a2054bcdb2304ece/janusgraph-dist/src/assembly/static/bin/gremlin.bat#L119 I see use of the deprecated

Hi Vinayak, This question is probably better addressed to: https://cassandra.apache.org/community/ as I cannot remember having seen this discussed in the JanusGraph community. Best wishes, Marc

Hi Vinayak, For embedded use of janusgraph, see: https://docs.janusgraph.org/getting-started/basic-usage/#loading-with-an-index-backend and replace the properties file with the one currently used by

Hi Marc, I went through some blogs but didn't get a method to connect to janusgraph using embedded mode using java. We are using Cassandra as a backend and cql to connect to it. Not sure how I will be

Hi Marc, The article was useful and complete the JMX authentication successfully. But when I allow password authentication for Cassandra by changing the following lines in Cassandra.yaml, it stops

Hi Naresh, I too used to get this exception. This was solved after moving to Janusgraph v0.5.2. Hope this helps you. Thanks, Abhay

Hi Naresh, Yes, elasticsearch, I should have recognized the "painless" scripting! This can mean the following things: your use case is maybe unusual, would it be possible to introduce a groupby step

Hello Marc, Thanks for quick reply. Am not using gremlin server. Am using spark, and read all messages per batch Then open JanusGraph transaction add batch records and commit it. Here is the

Hi Naresh, I guess that the script that the error message refers to, is the script that your client executes remotely at gremlin server. You may want to

Hi Boxuan, Thanks for pointing this out. Now I can provide this link when needed. Then, there are still broken links to RelationIdentifier in janusgraph-core, see the last link in my original

Hi, we are using janusgraph ( version 0.3.2) with elastic 6. when updating a node/vertex with property of LIST cardinality which is mixed index frequently getting below exception and data is not

Apart from rewriting the query, there are some config options (https://docs.janusgraph.org/basics/configuration-reference/#query) worth trying: 1) Turn on query.batch 2) Turn off query.fast-property

Hi Marc, Vinayak query has a filter on inV property (property1 = B), hence I did not stop at edge itself. If this kind of query is frequent, decision can be made if the same value makes sense to keep

It’s available here:

Hi Vinayak, As the link shows, the issue is an issue in TinkerPop, so it cannot be solved here. Of course, you can look for workarounds. As sending result sets of multiple hundreds of Mb is not a

As of janusgraph 0.5.0 the RelationIdentifier seems to be missing from the

Hi all, I also thought about the vertex centrex index first, but I am afraid that the VCI can only help to filter the edges to follow, but it does not help in counting the edges. A better way to

Hi Vinayak, For query 1. What is the degree centrality of vertex having property A. How much percentage satisfy out edge having property E. If it is small, VCI will help to increase speed for this

Hi All, We are connecting to janusgraph using java. A cluster connection with the gremlin driver is used for the connectivity. At the start, we were getting out of memory error, but tweaking some

Hi Saurabh, The workaround you found has implications for performance. So, if you can describe how to reproduce the issue, you can make an issue for it on