-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic fields term set query not working #4945
Comments
Thanks for the report @camerondavison @trinity-1686a, can you look at this? |
it looks like this is an issue of TermSetQuery not going through the tokenizer, and not lowercasing the values. Note that term set query with only a few elements is often less efficient than ORing a couple of term queries, so using a term set query for a set of 2 elements is not advisable. |
Yes that worked. Good to know about the OR v term set query. That seems a little counter intuitive TBH thanks. |
sets get efficient when you start to have many terms. Computation-wise, both should be close, but network-wise, multiple term queries will cause multiple small downloads, while term set will download a big chunk of data. When you have many terms in you set, one large fetch is more efficient than thousands of small fetches, but when you need only a few terms, doing these small fetches is faster. In the future, we may improve term set queries so they are more efficient when only a few terms can be requested. |
I am able to get
query to work, but I cannot get a term set query to work, like
This is my kafka ingestion configuration
Im not sure if it may be a feature or a bug, based on the dynamic json fields that it is trying to use.
The text was updated successfully, but these errors were encountered: