You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running into an issue after creating an index with an n_gram tokenizer with the token_chars field when using the below method to get all the indices in the cluster. The specific settings I'm using at create time are:
and performing the call you provided simply returns the list of all indices settings.
I have a request: could you try getting that specific index, like this?
esClient.indices()
.get(r -> r.index("ngram-test") // or your index name
.allowNoIndices(true)
.expandWildcards(ExpandWildcard.Open, ExpandWildcard.Closed))
.result()
Since you're getting all indices it could be another index that's causing the problem, and not the newly created one?
Also I have to ask, since this is pretty weird, are you super sure the version of the client is 8.16.1 and it's not clashing with any other version?
Hey @l-trotta, I just re-ran my test and it looks like I had something in cache that was keeping my client version at 8.14.3, can confirm that this is fixed!
Java API client version
8.16.1
Java version
17
Elasticsearch Version
8.14.3
Problem description
I'm running into an issue after creating an index with an n_gram tokenizer with the token_chars field when using the below method to get all the indices in the cluster. The specific settings I'm using at create time are:
Then using the get indices endpoint like below:
Throws with:
I would expect this to be patched by #877, but it doesn't look like it is.
The text was updated successfully, but these errors were encountered: