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.

Sign up for GitHub

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

Jump to bottom

Fix field type compatiblity check to work when only one previous type exists #12779

Merged
merged 1 commit into from Aug 11, 2015
Merged

Fix field type compatiblity check to work when only one previous type exists #12779

merged 1 commit into from Aug 11, 2015

Commits on Aug 10, 2015

  1. Mappings: Fix field type compatiblity check to work when only one pre… 

    …vious type exists.

This was a straight up bug found in elastic#12753. If only one type existed,
the compatibility check for a new type was not strict, so changes to
an updateable setting like search_analyzer got through (but only
partially). This change fixes the check and adds tests (which were
previously a TODO).

This also fixes a bug in dynamic field creation which woudln't copy
fielddata settings when duplicating a pre-existing field with the
same name.

closes elastic#12753
    @rjernst
    rjernst committed Aug 10, 2015
    Configuration menu
    Copy the full SHA
    b47f597 View commit details
    Browse the repository at this point in the history