-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
ESQL: Rename AUTO_BUCKET to just BUCKET #107197
Conversation
This renames the function AUTO_BUCKET to just BUCKET.
Documentation preview: |
Pinging @elastic/es-analytical-engine (Team:Analytics) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - just one, potentially important remark :)
* experimental:[] <<esql-auto_bucket>> | ||
* <<esql-bucket>> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it intended that we declare BUCKET
as released in this PR?
(If so, let's add this to the PR description as it's important IMHO.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it intended that we declare BUCKET as released in this PR?
Yes, I believe we wanted to decide on the naming, also considering the non-auto version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM however please wait for Andrei's review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks, Alex, Costin, Andrei. |
## Summary Close #180061 Key fixes - `auto_bucket` - now just called `bucket` as of elastic/elasticsearch#107197 - now accepts dates for the 3rd and 4th parameters - now accepts a number field for the first parameter - Constant-only parameters - We no longer suggest fields or variables for `auto-bucket`'s 2nd, 3rd, and 4th parameters, all of which must be constants - Validator catches non-constants even if they are nested in layers of functions (e.g. `auto_bucket(@timestamp, abs(length(bytes)), "", "")`) Outstanding issues - [x] Validation catches fields in a constant-only parameter spot, but not if they are nested in a function <img width="600" alt="Screenshot 2024-04-10 at 11 31 38 AM" src="https://github.com/elastic/kibana/assets/315764/3b73419a-f9d1-4d59-a128-b0135eb50a90"> _Validator sees the problem_ <img width="600" alt="Screenshot 2024-04-10 at 11 31 14 AM" src="https://github.com/elastic/kibana/assets/315764/1b5b0999-a697-4625-a8a3-15415054200b"> _Validator doesn't see the problem_ ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Stratoula Kalafateli <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
This renames the function
AUTO_BUCKET
to justBUCKET
.It also removes the experimental tagging of the function in the docs, making it generally available.