Fixed inconsistency in the isSyntheticSourceEnabled flag #137297
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses #136345.
Note, this only addresses the new edge case described in the issue. The existing edge cases around
FieldMapper.Builderare still present, but arguably are not as significant. For more context, read the issue above.Luckily, only text fields were impacted by by this, as they're the only ones using
builder.isSyntheticSourceEnabled()when initializing a field type. Keyword, match only text, annotated text, etc., all useMappingBuilderContextfor that information.