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.

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

[8.16] Add ECS known issue for ecs@mappings and fieldless searches (backport #1330) #1438

Merged
merged 2 commits into from
Nov 6, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 5, 2024

Update the 8.13 release notes to add a known issue.

Due to changes introduced to support the ecs@mappings component template (see https://github.com/elastic/kibana/pull/174855[elastic/kibana/pull/174855), Fleet no longer includes ECS fields to the integrations' index.query.default_field.

This may affect integrations that rely on fieldless queries (when no field is specified for a query).

This PR updates the 8.13 release notes to

  • acknowledge the problem
  • inform users that 8.14 is not affected
  • suggest a workaround to 8.13 users

Relates elastic/integrations#10848


This is an automatic backport of pull request #1330 done by Mergify.

* Add known issues about fieldless searches

* Fix section IDs and cleanup

* Add the known issue to 8.13.3 and 8.13.4

All 8.13.x releases are affected.

* Update docs/en/ingest-management/release-notes/release-notes-8.13.asciidoc

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>

* Apply suggestion from reviewers

---------

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
(cherry picked from commit f3e0dd1)
@mergify mergify bot requested a review from a team as a code owner November 5, 2024 16:53
@mergify mergify bot added the backport label Nov 5, 2024
@mergify mergify bot assigned zmoog Nov 5, 2024
Copy link

github-actions bot commented Nov 5, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@kilfoyle kilfoyle merged commit 84a8edd into 8.16 Nov 6, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants