-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Update migrate_8_16.asciidoc to include enrich.cache_size breaking ch… #118161
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
Conversation
…ange Heya, due to a bug found in elastic/sdh-elasticsearch#8603 a new breaking change was discovered with the enrich.cache_size setting changed to enrich.cache.size parameter. A Support KB now outlines the issue, https://support.elastic.co/knowledge/4821af0d. This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior.
Documentation preview: |
@ZachBrisson-Elastic please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-data-management (Team:Data Management) |
|
I think I created this confusion recently because I misunderstood, but we can actually just slap on backport tags and the automation will cherrypick to whatever version. So shouldn't need additional PRs. :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this, @ZachBrisson-Elastic! I left a comment regarding the phrasing of the breaking change, but I definitely agree we should add an entry.
I'm also adding @dakrone as a reviewer to pass a second pair of Data Management eyes on the change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I agree with Niels' suggestions
This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior.
This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior.
) This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior. Co-authored-by: Zach Brisson <[email protected]>
) This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior. Co-authored-by: Zach Brisson <[email protected]>
…ange
Heya, due to a bug found in https://github.com/elastic/sdh-elasticsearch/issues/8603 a new breaking change was discovered with the
enrich.cache_size
setting changed toenrich.cache.size
parameter. A Support KB now outlines the issue, https://support.elastic.co/knowledge/4821af0d.This commit adds an "Ingest changes" to the breaking changes section to outline this new behavior, outlining this new behavior. The devs have not confirmed but hope in 8.16.2 for both settings to be available
enrich.cache_size
(Presently only <8.16 worked) ANDenrich.cache.size
(Presently only >8.16 works). In a support case this stopped an upgrade entirely on elastic cloud. In self-hosted environments, it would result in an error triggering during the upgrade process.