-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[KQL] Remove number parsing #93658
[KQL] Remove number parsing #93658
Conversation
Pinging @elastic/kibana-app-services (Team:AppServices) |
Pinging @elastic/uptime (Team:uptime) |
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 for walking me through the changes
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
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @lukasolson |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
* [KQL] Remove number parsing * Update test snapshots
* [KQL] Remove number parsing * Update test snapshots
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
* [KQL] Remove number parsing * Update test snapshots Co-authored-by: Kibana Machine <[email protected]>
Summary
Fixes #48835.
Fixes #81581.
Fixes #85548.
Prior to this PR, when parsing a KQL expression, we would attempt to distinguish numbers from regular strings. This has been error-prone because of regex issues and handling numbers larger than JavaScript can handle. If we don't distinguish between strings and numbers, the queries that are generated and sent to Elasticsearch work regardless of whether they're passed as numbers or strings, so we can remove this behavior altogether.
Checklist
Delete any items that are not applicable to this PR.
For maintainers
Release note
KQL will no longer incorrectly parse unquoted strings as numbers.