-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
ES 5.3.0 + Kibana 5.3.0 => The [string] field is deprecated, please use [text] or [keyword] instead on [title] #10993
Comments
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? |
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 To make sure we are seeing the same thing. Can you repeat the manual step I shown in #10993 (comment) and don't touch any setting. Does |
@harobed To be clear: this is happening when you create a dashboard, right? Not just when you start elasticsearch/kibana? |
Yes ! |
I have the same problem, can you fix it? ELK 5.3.0 regards |
No fix :( |
I'm going to close this one out. Starting in 5.5 new .kibana indices will have updated mappings, implemented with #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.
|
I have this warning with Elasticsearch 5.3.0 and Kibana 5.3.0:
See:
The text was updated successfully, but these errors were encountered: