rngcntr

I did not see any further response on the mailing list about the usage of `limit()`. Does it mitigate the issue to use `limit()` right before `hasNext()`?

My point was that if this solves the issue, it would be an easy fix to deploy a strategy which replaces `hasNext()` by `limit(1).hasNext()` in every traversal.

Alright, got it. Thanks for the clarification!

Unreasonably large backend queries are the only reason I can imagine for batch processing to be disabled. +1 for `query.batch=true` and `query.limit-batch-size=true` by default.

`registerIndex` uses a timeout of 10 seconds to wait for the index operation to succeed. Given that the test executed successfully until now, I suspect that for some reason, the...

Hi @ChenZhaobin That's intended behavior. Have a look at the [docs](https://docs.janusgraph.org/index-backend/text-search/#full-text-search_1). It says: > `textContains`: is true if (at least) one word inside the text string matches the query string...

Nice to see your solution @ChenZhaobin! But I think the issue should stay open because the use of `hasLabel` should not impact the functionality of `textContains`.

Hi @porunov! What you describe as "precision score" is an estimation for the selectivity of a property. In my opening comment, I essentially refer to the same thing when talking...

@li-boxuan > Which index(es) will this new optimizer pick up, when we have `has(key1, value1).has(key2)` query and there is a composite index for `key1` and a mixed index for `key2`...

In your example, the new algorithm would take the index that is unique (if any) or just choose one of them otherwise. Regarding your other concern, I have to admit...