Skip to content

[8.19] Fix broken bwc logic in text field mapper introduced by #129126 (#129308) #129323

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

Merged
merged 2 commits into from
Jun 12, 2025

Conversation

martijnvg
Copy link
Member

elastic#129308)

A missing condition in the bwc logic caused a text field to be a stored, while before elastic#129126, this wasn't the case.
@martijnvg martijnvg added :StorageEngine/Mapping The storage related side of mappings >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport serverless-linked Added by automation, don't add manually Team:StorageEngine labels Jun 12, 2025
@elasticsearchmachine elasticsearchmachine merged commit bc00b12 into elastic:8.19 Jun 12, 2025
16 checks passed
@martijnvg martijnvg deleted the backport/8.19/pr-129308 branch June 12, 2025 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >non-issue serverless-linked Added by automation, don't add manually :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine v8.19.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants