Keyword type schema difference Elasticsearch 5.1 with 5.5

I have been using elasticsearch 2.X to 5.1 for quite some time for aggregation. The business logic does not need the string fields to be analysed.
In 5.1 when I set the field type as follows in the mapping template:
"myfield_name" : {
"type" : "keyword"
I can see in kibana management -> index pattern , the field definition is like this

But when I am trying out elasticsearch 5.5, the same setting of
"myfield_name" : {
"type" : "keyword"
Kibana index pattern shows there are two fields: myfield_name and myfield_name.keyword

Will it waste space in 5.5 to have two fields of different type to represent one field?
How can I define the schema to only have 1 field like elasticsearch 5.1?

Are you using Logstash?

Yes, I am using logstash 5.5

Then chances are that your template is not matching, and so the default Logstash one applies, which creates both a text and a keyword mapping of the field.

It'd be better if you raised another thread please.
That way we can help you directly and ask more relevant questions :slight_smile:

Done! Thank you and sorry :slight_smile:

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.