Skip to content

[8.x] synthetic source index setting provider should check source field mapper (#113522) #113717

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 1 commit into from
Sep 27, 2024

Conversation

martijnvg
Copy link
Member

Backports the following commits to 8.x:

…per (elastic#113522)

Adds logic to SyntheticSourceIndexSettingsProvider to check source field mapper to whether synthetic source is enabled.

Before this change the SyntheticSourceIndexSettingsProvider would only check the index.mode setting, which doesn't cover all usages of synthtic source.
@martijnvg martijnvg added :StorageEngine/Logs You know, for Logs >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:StorageEngine labels Sep 27, 2024
@elasticsearchmachine elasticsearchmachine merged commit c7e2b28 into elastic:8.x Sep 27, 2024
15 checks passed
@martijnvg martijnvg deleted the backport/8.x/pr-113522 branch September 27, 2024 19:22
dnhatn added a commit to dnhatn/elasticsearch that referenced this pull request Sep 29, 2024
@dnhatn dnhatn mentioned this pull request Sep 29, 2024
dnhatn added a commit that referenced this pull request Sep 29, 2024
…ield mapper (#113522) (#113717)" (#113746)

Revert "synthetic source index setting provider should check 
source field mapper (#113522) (#113717)"

This reverts commit c7e2b28.
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 :StorageEngine/Logs You know, for Logs Team:StorageEngine v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants