github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 06:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Remove version mention

Browse source 
Fixes #8708
This commit is contained in:
Andrew Cholakian 2017-11-22 07:23:06 -06:00
parent aa91b36da3
commit 1c0a909adc
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/static/upgrading.asciidoc vendored
View file

@ -72,7 +72,7 @@ We’d like to alert users to behavior in Logstash 6.0.0 that can cause errors w
`[2017-11-21T14:26:01,991][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :response=>{"error"=>{"reason"=>"Rejecting mapping update to [myindex] as the final mapping would have more than 1 type: [type1, type2]"}}}}`
The workaround for Logstash 6.0.0 is to add the setting `document_type => doc` to the Elasticsearch output configuration. Logstash 6.0.1+ will not require this workaround as that will become the new default behavior for Logstash when communicating with Elasticsearch 6.0+.
The workaround for Logstash 6.0.0 is to add the setting `document_type => doc` to the Elasticsearch output configuration. We will issue a patch to address this issue soon in a new version of Logstash.
Logstash has historically used the value of the `type` field to set the Elasticsearch `type` by default. Elasticsearch 6 [no longer supports more than one type]((https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html) per index. This is why the new behavior will only be applied to Elasticsearch 6.0 + clusters with our upcoming fixes.