I have this warning with Elasticsearch 5.3.0 and Kibana 5.3.0:
elasticsearch_1 | [2017-04-02T13:00:00,713][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [title]
elasticsearch_1 | [2017-04-02T13:00:00,715][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [timeFieldName]
elasticsearch_1 | [2017-04-02T13:00:00,716][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [intervalName]
elasticsearch_1 | [2017-04-02T13:00:00,718][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [fields]
elasticsearch_1 | [2017-04-02T13:00:00,720][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [sourceFilters]
elasticsearch_1 | [2017-04-02T13:00:00,721][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [fieldFormatMap]
elasticsearch_1 | [2017-04-02T13:00:00,723][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [title]
elasticsearch_1 | [2017-04-02T13:00:00,724][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [timeFieldName]
elasticsearch_1 | [2017-04-02T13:00:00,725][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [intervalName]
elasticsearch_1 | [2017-04-02T13:00:00,725][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [fields]
elasticsearch_1 | [2017-04-02T13:00:00,726][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [sourceFilters]
elasticsearch_1 | [2017-04-02T13:00:00,726][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [fieldFormatMap]
See:
Is that intended that in your image, you are using Kibana 5.2.2? https://github.com/harobed/elk_warning/blob/master/docker-compose.yml#L30
I did a manual test (without Docker):
wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.3.0.zip
unzip elasticsearch-5.3.0.zip
elasticsearch-5.3.0/bin/elasticsearch
wget https://artifacts.elastic.co/downloads/kibana/kibana-5.3.0-darwin-x86_64.tar.gz
tar xzf kibana-5.3.0-darwin-x86_64.tar.gz
kibana-5.3.0-darwin-x86_64/bin/kibana
I don't see anything in logs. Just the normal stuff... Can you share the full elasticsearch logs please?
Is that intended that in your image, you are using Kibana 5.2.2? https://github.com/harobed/elk_warning/blob/master/docker-compose.yml#L30
no, it's a mistake, I have same issue with ES 5.2.2 and Kibana 5.2.2.
I'm going to test with Kibana 5.3.0
Same error with Kibana 5.3.0, full log here : https://gist.github.com/harobed/926fedc89510dcd04da114572c5afe91
@harobed Apparently your elasticsearch node can be accessed externally by using 192.168.144.3:9200 address.
Are you sure you don't have any other older Kibana instance running somewhere which is trying to connect to your machine?
To make sure we are seeing the same thing. Can you repeat the manual step I shown in https://github.com/elastic/kibana/issues/10993#issuecomment-291002945 and don't touch any setting.
That way, we will be sure that no external machine is trying to connect to your elasticsearch instance. Make sure that you don't have any kibana process running locally though.
Does docker ps gives something else than elasticsearch an kibana?
Confirming this is likely caused by kibana - we don't have an upgrade process in place yet for mappings. Our changes for strings have made it into 6.0 via https://github.com/elastic/kibana/pull/9280, and will likely be added with https://github.com/elastic/kibana/issues/9930 to the 5.x line.
@harobed To be clear: this is happening when you create a dashboard, right? Not just when you start elasticsearch/kibana?
To be clear: this is happening when you create a dashboard, right?
Yes !
I have the same problem, can you fix it?
ELK 5.3.0
regards
I have the same problem, can you fix it?
No fix :(
I'm going to close this one out. Starting in 5.5 _new_ .kibana indices will have updated mappings, implemented with https://github.com/elastic/kibana/pull/10638. In 5.6 we introduced an upgrade assistant which will prepare the kibana index for 6.0 that will effectively fix this for existing indices. See https://www.elastic.co/guide/en/kibana/6.0/migrating-6.0-index.html for docs, note it requires installing x-pack or following a manual process.
If upgrading or installing x-pack isn't an option, you can perform a reindex on .kibana with the correct mappings.
1) Create an index template
curl -XPUT "http://localhost:9200/_template/kibana" -H 'Content-Type: application/json' -d'
{
"template": ".kibana-5*",
"settings": {
"number_of_shards": 1
},
"mappings": {
"config": {
"properties": {
"buildNum": {
"type": "keyword"
}
}
},
"index-pattern": {
"properties": {
"fieldFormatMap": {
"type": "text"
},
"fields": {
"type": "text"
},
"intervalName": {
"type": "keyword"
},
"notExpandable": {
"type": "boolean"
},
"sourceFilters": {
"type": "text"
},
"timeFieldName": {
"type": "keyword"
},
"title": {
"type": "text"
}
}
},
"visualization": {
"properties": {
"description": {
"type": "text"
},
"kibanaSavedObjectMeta": {
"properties": {
"searchSourceJSON": {
"type": "text"
}
}
},
"savedSearchId": {
"type": "keyword"
},
"title": {
"type": "text"
},
"uiStateJSON": {
"type": "text"
},
"version": {
"type": "integer"
},
"visState": {
"type": "text"
}
}
},
"search": {
"properties": {
"columns": {
"type": "keyword"
},
"description": {
"type": "text"
},
"hits": {
"type": "integer"
},
"kibanaSavedObjectMeta": {
"properties": {
"searchSourceJSON": {
"type": "text"
}
}
},
"sort": {
"type": "keyword"
},
"title": {
"type": "text"
},
"version": {
"type": "integer"
}
}
},
"dashboard": {
"properties": {
"description": {
"type": "text"
},
"hits": {
"type": "integer"
},
"kibanaSavedObjectMeta": {
"properties": {
"searchSourceJSON": {
"type": "text"
}
}
},
"optionsJSON": {
"type": "text"
},
"panelsJSON": {
"type": "text"
},
"refreshInterval": {
"properties": {
"display": {
"type": "keyword"
},
"pause": {
"type": "boolean"
},
"section": {
"type": "integer"
},
"value": {
"type": "integer"
}
}
},
"timeFrom": {
"type": "keyword"
},
"timeRestore": {
"type": "boolean"
},
"timeTo": {
"type": "keyword"
},
"title": {
"type": "text"
},
"uiStateJSON": {
"type": "text"
},
"version": {
"type": "integer"
}
}
},
"url": {
"properties": {
"accessCount": {
"type": "long"
},
"accessDate": {
"type": "date"
},
"createDate": {
"type": "date"
},
"url": {
"type": "text",
"fields": {
"keyword": {
"type": "keyword",
"ignore_above": 2048
}
}
}
}
},
"server": {
"properties": {
"uuid": {
"type": "keyword"
}
}
},
"timelion-sheet": {
"properties": {
"description": {
"type": "text"
},
"hits": {
"type": "integer"
},
"kibanaSavedObjectMeta": {
"properties": {
"searchSourceJSON": {
"type": "text"
}
}
},
"timelion_chart_height": {
"type": "integer"
},
"timelion_columns": {
"type": "integer"
},
"timelion_interval": {
"type": "keyword"
},
"timelion_other_interval": {
"type": "keyword"
},
"timelion_rows": {
"type": "integer"
},
"timelion_sheet": {
"type": "text"
},
"title": {
"type": "text"
},
"version": {
"type": "integer"
}
}
}
}
}'
2) Reindex
curl -XPOST "http://localhost:9200/_reindex" -H 'Content-Type: application/json' -d'
{
"source": {
"index": ".kibana"
},
"dest": {
"index": ".kibana-5.x"
}
}'
3) In kibana.yml change kibana.index: .kibana-5.x