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

Update CHANGELOG.asciidoc #174383

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Update CHANGELOG.asciidoc #174383

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 27 additions & 1 deletion docs/CHANGELOG.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]]
Expand Down