-
Notifications
You must be signed in to change notification settings - Fork 306
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
Mapping changes in Elasticsearch 5.0 for string field type #386
Comments
untergeek
added a commit
to untergeek/logstash-output-elasticsearch
that referenced
this issue
Mar 21, 2016
Do not use this with older versions of Elasticsearch. It will not work. fixes logstash-plugins#386
@untergeek and I worked with the ES team to make sure existing templates are backward compatible, so this is not going to be a big breaking change. We're gonna clean up existing template to work with 5.0 and also add an enhancement to auto-upgraed templates if ES 5.0 is used. |
suyograo
added a commit
to suyograo/logstash-output-elasticsearch
that referenced
this issue
Aug 4, 2016
suyograo
pushed a commit
that referenced
this issue
Aug 17, 2016
* Update template to use ES 5.x mapping Fixes #386
neumaics
added a commit
to MapQuest/logstash-output-elasticsearch
that referenced
this issue
Dec 19, 2016
Fix typo Update template to use ES 5.x mapping (logstash-plugins#462) * Update template to use ES 5.x mapping Fixes logstash-plugins#386 remove `force` as valid version type parameter remove trailing comma
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elasticsearch is changing
string
field to split them into two variants:keyword
andtext
. More info about this here: elastic/elasticsearch#12394The LS template should be changed to reflect this.
string_fields
rule in template should be split totext_fields
andkeyword_fields
rule. All thefields.raw
should be updated tokeyword
type and@message
should betext
.@version
should bekeyword
too.With this change, LS will be locked with ES version, even with HTTP protocol because this change is not backward compatible.
The text was updated successfully, but these errors were encountered: