Hi, how can I fix this ElasticSearch 5.2.2 Warning? [WARN ][o.e.d.i.m.MapperService ] [unmapped_type:string] should be replaced with [unmapped_type:keyword] This is my indices configuration: https://gist.github.com/harobed/e92fb7d131cac523067c26458d842184 Best regards, Stéphane

Read the breaking changes doc. String type has been removed.

[image] dadoonet: Read the breaking changes doc. String type has been removed. I use Logstash 5.2.2 and Kibana 5.2.2 on empty ES. This two tools are not compatible with ES 5.2.2 ?

They are but you probably upgraded or already have an old template?

[image] dadoonet: They are but you probably upgraded or already have an old template? No, my data are empty.

ES display that warning for logstash indice: elasticsearch_1 | [2017-03-27T19:25:37,644][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [title] elasticsearch_1 | [2017-03-27T19:25:37,649][WARN ][o.e.d.i.m.StringFieldMappe…

It can be that? curl "http://localhost:9200/logstash-2017.03.27/?pretty=1" { "logstash-2017.03.27" : { "aliases" : { }, "mappings" : { "_default_" : { "_all" : { "enabled" : true, "norms" : false }, "dynamic_templates" : [ { …

But this template is correct. Can you run a get cluster state query?

[image] dadoonet: Can you run a get cluster state query? This gist:5c196be791eace13e343409907e780a6 · GitHub ?

Weird. I can't explain what you are seeing here. BTW how do you know that the messages you saw are related to logstash or kibana indices? Any chance you have old kibana instance which is trying to connect to your Elasticsearch cluster? Same for logstash?

I checked what Logstash 5.2.2 is sending to elasticsearch and it looks correct to me: https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/5.2.x/lib/logstash/outputs/elasticsearch/elasticsearch-template-es5x.json

[WARN ][o.e.d.i.m.MapperService ] [unmapped_type:string] should be replaced with [unmapped_type:keyword]

Elastic Stack Elasticsearch

klein_stephane (Stéphane Klein) March 28, 2017, 2:38pm 12

I did:

$ rm es-data -rf

before restart my ES Docker. Then I think ES is empty

Topic		Replies	Views
The [string] field is deprecated Elasticsearch	3	2140	June 22, 2017
Timeseries indices has type both string and text(or keyword) Kibana	3	434	April 6, 2017
ES5.0a1: The [string] type is removed in 5.0. You should now use either a [text] or [keyword] field instead for field Elasticsearch	14	5850	July 5, 2017
String Type in ES5.0 Elasticsearch	3	596	February 22, 2017
No handler for type [string] declared on field [fieldname] Elasticsearch	1	3833	April 6, 2020

[WARN ][o.e.d.i.m.MapperService ] [unmapped_type:string] should be replaced with [unmapped_type:keyword]

Related topics