github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update CHANGELOG.asciidoc

Browse source 
added known KQL bug to release notes: https://github.com/elastic/kibana/issues/169709
This commit is contained in:
Roberto Seldner 2024-01-05 11:44:03 -07:00 • committed by GitHub
parent 963af9f0b7
commit 72f1bde7a8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 27 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

28
docs/CHANGELOG.asciidoc
View file

@ -59,7 +59,33 @@ Review important information about the {kib} 8.x releases.
[[release-notes-8.11.3]]
== {kib} 8.11.3
The 8.11.3 release includes the following bug fixes.
For information about the Kibana 8.11.3 release, review the following information.
[float]
[[known-issues-8.11.3]]
=== Known issues
// tag::known-issue-xxxxxx[]
[discrete]
Incorrect backslash escaping on keyword wildcard questions {kibana-issue}169709[#169709].
[%collapsible]
====
*Details* +
Support for wildcard queries in KQL was introduced in 8.5. {kibana-pull}}140629[#140629]
It appears that backslashes are not properly re-escaped when providing them to a wildcard query.
When running a KQL wildcard query for a keyword field that contains backslashes, such as `field: \*\\\*`, they have to be double-escaped to produce the expected results.
*Impact* +
Results for `field: \*\\\*` are not returned.
*Workaround* +
Double escape the slashes `field: \*\\\\\*`.
====
// end::known-issue-xxxxxx[]
[float]
[[fixes-v8.11.3]]