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

The _all default mapper is not completely configured. #22236

Merged
merged 1 commit into from
Dec 19, 2016

Conversation

jpountz
Copy link
Contributor

@jpountz jpountz commented Dec 16, 2016

In some cases, it might happen that the _all field gets a field type that is
not totally configured, and in particular lacks analyzers. This is due to the
fact that AllFieldMapper.TypeParser.getDefault uses Defaults.FIELD_TYPE as
a default field type, which does not have any analyzers configured since it
does not know about the default analyzers.

In some cases, it might happen that the `_all` field gets a field type that is
not totally configured, and in particular lacks analyzers. This is due to the
fact that `AllFieldMapper.TypeParser.getDefault` uses `Defaults.FIELD_TYPE` as
a default field type, which does not have any analyzers configured since it
does not know about the default analyzers.
@jpountz jpountz added :Search Foundations/Mapping Index mappings, including merging and defining field types >bug labels Dec 16, 2016
Copy link
Contributor

@ywelsch ywelsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jpountz jpountz merged commit 96f1739 into elastic:master Dec 19, 2016
@jpountz jpountz deleted the fix/all_defaults branch December 19, 2016 08:54
jpountz added a commit that referenced this pull request Dec 19, 2016
In some cases, it might happen that the `_all` field gets a field type that is
not totally configured, and in particular lacks analyzers. This is due to the
fact that `AllFieldMapper.TypeParser.getDefault` uses `Defaults.FIELD_TYPE` as
a default field type, which does not have any analyzers configured since it
does not know about the default analyzers.
jpountz added a commit that referenced this pull request Dec 19, 2016
In some cases, it might happen that the `_all` field gets a field type that is
not totally configured, and in particular lacks analyzers. This is due to the
fact that `AllFieldMapper.TypeParser.getDefault` uses `Defaults.FIELD_TYPE` as
a default field type, which does not have any analyzers configured since it
does not know about the default analyzers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Search Foundations/Mapping Index mappings, including merging and defining field types v5.1.2 v5.2.0 v6.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants