Have you tried https://docs.janusgraph.org/basics/transactions/#transaction-configuration ? It allows you to enable/disable storage.batch-loading per transaction.

Hi Frederick, This is a good question, but I have no answer. For myself, I have always take a fresh janusgraph instance if I wanted to change one of the properties! Best wishes, Marc

Hi Umesh, I read this yesterday and thought your reasoning was sound, but at the same time it seemed unlikely it was in the ref docs for no reason. Just now, a scenario appeared to me where both locks

It works well with version 0.6.0-SNAPSHOT. hope the realease version come soon

Sorry I misunderstood your problem. I thought you have a cluster with different transport ports, which is not supported prior to Cassandra 4. Turns out your cluster is using a uniform non-default

Got it. It does not seem to be a JanusGraph problem. I didn’t dig deep into it but seems it’s a limitation of Cassandra. See https://datastax-oss.atlassian.net/browse/JAVA-1388#icft=JAVA-1388 and

Hi All, To avoid a situation of duplicate vertex creation due to parallel transactions, we are using index uniqueness over property which defines uniqueness of vertex. As per doc, we need to

Hi， I am sorry to make you confused. I get the line number 220 from a .class file, not a .java file. the line number in java file is 246. you can read it from the screenshot but I don't mean this

I am a bit confused here. In fed8439, CQLStoreManager.java#L220

I have gone through the commit, I think that will help. To confirm we need to test it with the master branch as it has been not released yet. Earlier, we downloaded the full version from the releases

Yes. We face same issue when using custom ports with C* backend. The first host:port in storage.hostname is processed correctly. For the remainder of comma separated host:port, JanusGraph tried to

The janusgraph will try to connect with 192.168.223.3:9042 I find the codes in janusgraph-cql-0.5.3.jar， the codes is: final Builder builder = Cluster.builder()

What happens when you only use “192.168.223.3” as your storage.hostname, and don’t set storage.port? I am also not sure about what version of line 220 you are looking at. What is the commit

Hi， the version is 0.53，and the line is line 220 in org.janusgraph.diskstorage.cql.CQLStoreManager The cluster builder's port is default 9042. when I set one host,the logs are the same.if I set

Hi, I am not sure what code you think is problematic. Can you provide 1) your JanusGraph version, and 2) the specific line(s) that you believe a bug exists? What happens if you only provide only ONE

Thanks Florian for sharing these details ! Best regards, Dev

Hi Dev, you can follow the progress here: https://github.com/JanusGraph/janusgraph/pull/2672 There is no ETA, but we are planning to release 0.6.0 as soon as possible. It is currently blocked by a

Hi Boxuan, If possible can you please share 0.6.0 tentative release date? This would help us in planning updates. Thanks Dev

hi， all the nodes have the same port。one of the nodes can keep the correct port, the others will be changed to 9042. the code is in org.janusgraph.diskstorage.cql.CQLStoreManager and in this

Could you check your query on master branch?Possibly this https://github.com/JanusGraph/janusgraph/commit/7550033d1746d0844bac79e3a8b85685c2c6c79d fix improve this type of query