We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Kibana version: 7.6.1 Elasticsearch version: 7.6.1 Server OS version: Windows 2012R2 Browser version: Chrome 80 Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): Download
Describe the bug: KQL seems to silently remove leading zeros causing queries to fail.
When querying "customer: 00123" with Lucene we get results but KQL removes the leading zeros:
"filter":[{"bool":{"should":[{"match":{"customer":12282650}}]...
Lucene Query generates:
{"bool":{"must":[{"query_string":{"query":"customer: 0012282650","analyze_wildcard":true,"time_zone"...
Field type customer is keyword.
The text was updated successfully, but these errors were encountered:
Pinging @elastic/kibana-app-arch (Team:AppArch)
Sorry, something went wrong.
alexwizp
Successfully merging a pull request may close this issue.
Kibana version: 7.6.1
Elasticsearch version: 7.6.1
Server OS version: Windows 2012R2
Browser version: Chrome 80
Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): Download
Describe the bug:
KQL seems to silently remove leading zeros causing queries to fail.
When querying "customer: 00123" with Lucene we get results but KQL removes the leading zeros:
Lucene Query generates:
Field type customer is keyword.
The text was updated successfully, but these errors were encountered: