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
it looks like this is an issue of TermSetQuery not going through the tokenizer, and not lowercasing the values. @camerondavison can you confirm you use the default tokenizer, and that data.event_type:IN [standardmgaquoteissued quoteissued] returns the result you expect?
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.
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: