Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[KQL] Enable equals (=) operator for exact match #157446

Closed
Tracked by #166068
lukasolson opened this issue May 11, 2023 · 1 comment
Closed
Tracked by #166068

[KQL] Enable equals (=) operator for exact match #157446

lukasolson opened this issue May 11, 2023 · 1 comment
Labels
discuss Feature:KQL KQL Icebox impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated papercut Small "burr" in the product that we should fix. Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@lukasolson
Copy link
Member

Currently, KQL only allows using the colon : operator for "match" queries and inequality operators (<, >, >=, <=) for range queries. This introduces confusion for users attempting to use = for "match" queries, since it is not currently accepted as an operator. This means that a query such as response = 200 will actually result in a query searching all fields for the value of response = 200 instead of filtering for documents where the response field is 200.

This issue is intended to be a discussion of whether we'd like to introduce the = operator for an "exact match" syntax, to alleviate the confusion for our users.
@lukasolson lukasolson added Feature:KQL KQL Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. papercut Small "burr" in the product that we should fix. labels May 11, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@davismcphee davismcphee added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated labels Sep 8, 2023
@kertal kertal mentioned this issue Oct 1, 2024
Open
@kertal kertal added the Icebox label Oct 1, 2024
@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss Feature:KQL KQL Icebox impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated papercut Small "burr" in the product that we should fix. Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kertal @lukasolson @elasticmachine @davismcphee