-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Support case_insensitive for 'Include' of Terms Aggregation #68819
Comments
Pinging @elastic/es-analytics-geo (Team:Analytics) |
Is there any update on this ? |
@cbuescher can someone take a look at this please. |
If this is being ignored because there is some easy workaround, please enlighten me |
Hi, |
Thanks @awenger63 I think that may work but then someone would raise a bug that the values are all lowercase, I will try thinking of a reliable way to fix the casing in code afterwards. |
Hey! I've been ignoring this one just because I can't read all the things and I figured someone else on the team was doing it. I was wrong. Anyway, would something this do what you want?
Its certainly not the simplest work around because you have to lean on runtime fields and write a script instead of set a single setting but it does give you a bunch of flexibility. I think the script itself won't dominate the runtime here - I think you'll see the |
Thanks @nik9000 I'll give this workaround a go when I get a chance. Do you think there is much chance of this proposal getting worked as considering it's lack of complexity ? |
I think it's the kind of thing that we'd take a contribution for but won't have time to build ourselves. At least, I don't have time and don't know anyone who does. I think I made a mess of the runtime field definition in my comment above. Sorry. I'll have to refer you to the docs to correct my mistakes: https://www.elastic.co/guide/en/elasticsearch/reference/7.14/runtime-search-request.html . That's what i get for trying to write a request at 7:45 without enough coffee in me. |
I noticed the recent 7.10 release bringing support for case insensitivity to more parts of the DSL (61546 & 59441)
I require the ability to filter Terms Aggregation buckets in a case-insensitive way.
The text was updated successfully, but these errors were encountered: