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

Thank you ! Currently, we have only a limited set of features to support from ES, so we are most likely going to wrap the Janus' text predicates. All the best, Flo

Hi, Can you check your cassandra nodes’ configurations? It looks like some of your nodes are still using 9042 for native transport port. Cheers, Boxuan 「<zhouyu74748585@...>」在 2021年6月17日

Hi Flo, Elasticsearch Index is only used when your query is a global query (a.k.a. graph-centric query in JanusGraph), i.e. look up vertices with conditions. `traversal.V().has(…)` is a global

Hi Kumkar, There is no standard process. I would suggest creating a [Feature Request] type issue: https://github.com/JanusGraph/janusgraph/issues/new?assignees=&labels=&template=feature-request.md

Thanks Boxuan this really helps ! Can you please help with pointers to create GitHub issue for any EOL version? Thanks Dev Kumkar

Hi Kumkar, The incoming 0.6.0 release contains (but not limited to) the following updates: hppc: 0.8.0 noggit: 0.8 commons-configuration2: 2.7 commons-lang3: 3.11 You are welcome to create a GitHub

Hello We are using Janus 0.5.3 and there are some components which are either old or else EOL version being used. Old version used: hppc-0.7.1.jar jcabi-log-0.14.jar noggit-0.6.jar EOL version