Re: Count Query
Vinayak Bali
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 page(janusgraph-full-0.5.2) and moved forward. I am not sure how I can test the queries on the master branch. Please share the setups or any document regarding the same. Thank you.
On Fri, Jun 18, 2021 at 11:59 PM <owner.mad.epa@...> wrote: Could you check your query on master branch?Possibly this https://github.com/JanusGraph/janusgraph/commit/7550033d1746d0844bac79e3a8b85685c2c6c79d fix improve this type of query
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
Ronnie
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 connect to those servers with the default port of 9042. We had this problem since JanusGraph 0.4.x was hoping this would be fixed by 0.5.3, but this issue still exist.
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
zhouyu74748585@...
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() .addContactPointsWithPorts(contactPoints) .withClusterName(configuration.get(CLUSTER_NAME)); //.withPort(configuration.get(CLUSTER_PORT));
in branch V0.5 fed8439 I append the last line to solve this problem,but it only work when all the host have same port;
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
Boxuan Li
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 hash? You can also just copy the code snippet here. 「<zhouyu74748585@...>」在 2021年6月22日 週二,上午9:42 寫道:
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
zhouyu74748585@...
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.
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
Boxuan Li
Hi,
toggle quoted messageShow quoted text
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 host:port in the “storage.hostname”? Do you still see the same log? I am asking because the log you provided comes from DataStax Driver, not JanusGraph. The DataStax driver tries to connect to the cluster via the entry points you provide, even though the entry points are not a complete or correct set of all hosts. The driver then fetches meta data from the cluster and prints logs like “New Cassandra host XX added”. Thus, I suspect not every host in your Cassandra cluster uses 9042 port.
|
|
|
|
Re: EOL version components
kumkar.dev@...
Thanks Florian for sharing these details !
Best regards, Dev
|
|
|
|
Re: EOL version components
Hi Dev, There is no ETA, but we are planning to release 0.6.0 as soon as possible. It is currently blocked by a TinkerPop issue: https://issues.apache.org/jira/browse/TINKERPOP-2579
|
|
|
|
Re: EOL version components
kumkar.dev@...
Hi Boxuan,
If possible can you please share 0.6.0 tentative release date? This would help us in planning updates. Thanks Dev
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
zhouyu74748585@...
hi, the cluster builder has a default port 9042,and finally return a cluster with port 9042, the port in configurations will not be use.
|
|
|
|
Re: Count Query
owner.mad.epa@...
Could you check your query on master branch?Possibly this https://github.com/JanusGraph/janusgraph/commit/7550033d1746d0844bac79e3a8b85685c2c6c79d fix improve this type of query
|
|
|
|
Re: Custom analyzer with traversal queries
florent@...
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
|
|
|
|
Re: Failed to connect to a Cassandra cluster's all nodes without default port
Boxuan Li
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日 週四,下午4:39 寫道:
|
|
|
|
Re: Custom analyzer with traversal queries
Boxuan Li
Hi Flo,
toggle quoted messageShow quoted text
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 query. On the other hand, `traversal().V(idx1, idx2, …).has(…)` is a vertex-centric query rather than global query. Elasticsearch is not involved, thus your custom analyzers are not used. Your observations are valid. The documentation is not very clear indeed. Unfortunately I don’t see any workaround here. Probably you could modify Text.java and build your own JanusGraph. You may also want to create a feature request to allow custom analyzers without indexing backends. Probably we could make Text.java pluggable (not sure if that’s possible). Best regards, Boxuan
|
|
|
|
Re: EOL version components
Boxuan Li
Hi Kumkar,
toggle quoted messageShow quoted text
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 You may want to state which libraries are in EOL, and preferably link to their EOL statements/documentation. I recommend checking the dependency version on master branch first before reporting. Best regards, Boxuan
|
|
|
|
Re: EOL version components
kumkar.dev@...
Thanks Boxuan this really helps !
Can you please help with pointers to create GitHub issue for any EOL version? Thanks Dev Kumkar
|
|
|
|
Re: EOL version components
Boxuan Li
Hi Kumkar,
toggle quoted messageShow quoted text
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 issue for any EOL version you observe that is still being used by JanusGraph. Best regards, Boxuan
|
|
|
|
EOL version components
kumkar.dev@...
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:
EOL version used:
Thanks Dev Kumkar
|
|
|
|
Failed to connect to a Cassandra cluster's all nodes without default port
zhouyu74748585@...
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.
|
|
|
|
Custom analyzer with traversal queries
florent@...
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
|
|
|