-
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
Extend allowed characters in aggregation name #6702
Comments
Not understaning the reason why only alpa-numeric chars are allowed, wouldn't it be possible to allow any char by internally working with hexadecimal encoded strings? I would really wish, that arbitrary chars would still be allowed. My current workaround is to do the hex encoding manually. My aggregation names are computed dynamically and are displayed on the frontend, so avoiding non-alpha-numerics is not an option for me. ("cross-posted" from #5253) |
@colings86 What about allowing escaping of dots? eg "foo.bar.baz" (as JSON "foo\.bar.baz")? |
relates to #6736 |
Aggregation name are now able to use any character except '[', ']', and '>". Dot syntax may still be used to reference values (e.g. in the order field) but may only defence the value directly beneath the last aggregation in the list. more complex structures will need to be accessed using the aggname[value] syntax Closes #6702
Good job! |
This will be available from version 1.3 as 1.2.2 is intended for bug fixes. We try to release every couple of months, but it depends on the features we are working on. We don't announce release dates ahead of time. |
Hi, I'm trying to use bucket selection with over an aggregation whose name contains numerical characters. Same error has been occurred for me. I realized that aggregations with numeric characters has been solved but I think there is still an error for bucket selection. Is there a way to solve this? Error:
My query:
|
Currently aggregations names must match the pattern
[a-zA-Z0-9\\-_]+
. This is pretty restrictive and prevents, for example, a common naming pattern of using dots in names. We should extend this pattern to be less restrictive.Currently an aggregation can refer to values within child aggregations using two methods:
Allowing dots in the aggregation name will mean that we drop support for option 2 in favour of 1.
The text was updated successfully, but these errors were encountered: