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 three hosts,janusgraph only chose one to connect to cassandra cluster。

janusgraph gets other ips from cluster's metadata.but use the default port 9042 in the local 

cluster object,then the local cluster try to connect to the host with correct ip and default port.

 

On Jun 21, 2021, at 4:00 PM, zhouyu74748585@... wrote:

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 method Cluster initializeCluster()

the cluster builder has a default port 9042，and finally return a cluster with port 9042, the port in configurations will not be use.

Hello everyone, when I try to connect to a Cassandra cluster which's port is not default, just like this  StandardJanusGraph graph = (StandardJanusGraph) JanusGraphFactory.build().set("storage.backend", "cql"). set("storage.hostname", "192.168.223.3:51705,192.168.223.4:51705,192.168.223.5:51705,"). open();

but when I start it，

only one node's is correct, the others' port change to 9042, the default one. so I can only connect to one node.
I try to fix this, but it only useful when all nodes' port are the same.if different node has different port.it will not work.
So I hope someone will have a good solution.

On Jun 17, 2021, at 3:56 PM, florent@... wrote:

Hello everyone,


As it's my first post, I'd first thank you all for your work ! It has been pretty neat to discover all of the work !

We've started to investigate the use of custom analyzers in our schema (-> https://docs.janusgraph.org/v0.5/index-backend/field-mapping/#for-elasticsearch), where ES is used as an indexing backend.

From what I've seen, initial selections will indeed use the index (e.g. `traversal().V().has(...)`). However, it isn't always used, and sometimes the janusgraph implementation of the predicate is used (e.g. when `traversal().V(idx1, idx2, ...).has(...)`). In this latter case, it's the predicates as implemented here that are run. For text fields, it looks like a tokenization and lower-casing are perform by them directly.

I haven't seen mention of this case in the documentation. So, I'm wondering if my observations are valid.

If so, is there a way to force the usage of ES indices? An IDs query could be way to implement such feature (at least for ES).


All the best,
Flo

On Jun 17, 2021, at 9:57 PM, kumkar.dev@... wrote:

Thanks Boxuan this really helps !

Can you please help with pointers to create GitHub issue for any EOL version?

Thanks
Dev Kumkar

On Jun 17, 2021, at 9:35 PM, kumkar.dev@... wrote:

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 used:

• commons-collections-3.2.2.jar
• commons-configuration-1.10.jar
• commons-lang-2.6.jar
• javapoet-1.8.0.jar

Are there any upcoming updates which could be shared here pointing when and which of these components would be updated?

Thanks
Dev Kumkar