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

Backport: Set strings to be keywords by default (#2688) #2696

Merged
merged 1 commit into from
Oct 5, 2016
Merged

Backport: Set strings to be keywords by default (#2688) #2696

merged 1 commit into from
Oct 5, 2016

Commits on Oct 5, 2016

  1. Set strings to be keywords by default (elastic#2688) 

    This adds a dynamic mapping to all our template files to set strings to be
keywords by default.

Previously we were using the default of `text` and only switching to `keyword`
when configured in `fields.yml`. This reverses the logic and sets mappings to
`text` only when requested in `fields.yml`.

The goal is to make upgrading the mapping template less painful. In the Beats
we have so far, unexpected fields are better of as keywords.
    @tsg
    tsg authored and Tudor Golubenco committed Oct 5, 2016
    Configuration menu
    Copy the full SHA
    aa449b4 View commit details
    Browse the repository at this point in the history