Hi Sujay, I am not sure about the root cause (it might be a JanusGraph bug or a Datastax CQL driver bug), but you could try the JanusGraph 0.6.0 version and disable the `storage.cql.executor-service.e

Hi Mladen, I can confirm this is indeed a bug. I apologize that when writing the test, I didn't notice the second open call was just returning the cached instance. Thank you for reporting and fixing i

Hi Mladen, As Marc pointed out, this scenario is tested in the JanusGraph codebase. I noticed your error log contains: 2021-09-21 14:11:15,347 [pool-12-thread-1] com.datastax.oss.driver.internal.core.

Hi Radhika, Got it. You are right, you need to reopen the graph after setting `tx.log-tx`.

Hi, I didn't check your metrics but my first impression was this might be related to the internal thread pool. Can you try out the 0.6.0 pre-release version or master version? Remember to set `storage

I suspect this is due to stale management instances. Check out https://developer.ibm.com/articles/janusgraph-tips-and-tricks-pt-2/#troubleshooting-indexes and see if it helps.

Hi Toom, Do you want to ALWAYS make sure the vertex is indexed? If so and if you happen to use Elasticsearch, you can set See https://www.elastic.co/guide/en/elasticsearch/reference/master/docs-refres

Hi Radhika, Unfortunately, there is no such API. If you are willing to dive into JanusGraph source code, you can modify StandardTransactionLogProcessor::fixSecondaryFailure method and build JanusGraph

No. It should work well for your existing JanusGraph setup too. Note that it is a GLOBAL option so it must be changed for the entire cluster. See https://docs.janusgraph.org/basics/configuration/#glob

Hi Vinayak, Would you be able to build JanusGraph from master branch and try again? The upcoming 0.6.0 release contains many optimizations which might be helpful. Without knowing more details of your

The difference between “text” and “string” is explained here: https://docs.janusgraph.org/index-backend/text-search/ In short, “text” is for full-text search (tokenized search) capability while “strin

Looks like this is because you are indexing your property as text. See https://docs.janusgraph.org/index-backend/text-search/#full-text-search_1 I believe the query has(“country", P.neq(null)) would w

Can you show the profile output? Just add .profile() to the end of your query. 「Laura Morales <lauretas@...>」在 2021年7月23日 週五，下午4:13 寫道：

Try rewriting your query as: ` g.V().has("country", P.neq(null)).values("country").dedup().order().limit(10)` FYI starting from the upcoming 0.6.0 release, has("country") will leverage the mixed index

Hi, it means your query is not leveraging your indexes. Can you provide the query and also the output of `mgmt.printIndexes()` (or how you created the indices)?

Hi Laura, unfortunately, you would have to handle this in your application layer. For example, you can use different labels, properties, indexes for different subgraphs.

That’s a great question! To be honest I am not sure about the reason. My assumption is the __.out("edgeCB").is("B") is an anonymous child traversal within where() step, and thus it has no access to th

Hi Ronnie, Not sure if it's optimal but this should work: g.V().hasLabel("VertexB").as("B").in("edgeAB").out("edgeAC").as("C").out("edgeCB").as("B2").where("B", eq("B2")).select("C") You can also do t

Hi, Seems you are the victim of https://github.com/JanusGraph/janusgraph/issues/2231. There is an open PR to fix this: https://github.com/JanusGraph/janusgraph/pull/2567 Best, Boxuan

Hi, is this the full stacktrace? Is there a nested exception?