-
Notifications
You must be signed in to change notification settings - Fork 8k
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
mapper [hits] cannot be changed from type [long] to [integer] #9888
Comments
+1 Are there any temporary solutions to this other than just deleting the .kibana index? |
I ended up just doing this:
|
For anyone else who runs into this issue I followed the suggestions on this page. Before importing the dashboard I am deleting the |
We are working on a fix scheduled for this in 5.6. It's usually caused by incorrect mappings. Kibana in versions < 5.5 pushes mappings as needed from the browser. If you are restoring a kibana index before these mappings have been created, dynamic mappings will be used and won't match what kibana expects causing errors like this. If you're on 5.x and running into this, as a workaround, I would recommend creating an index template with the correct mappings and then reindexing. Make sure to do backups before, and the steps below are a rough approximation:
|
@jbudz Finally, awesome thanks! Waiting version with fix |
The work around works great! Thanks for posting it :) |
This should not be an issue starting in 6.0 as we only have a single type and this issue is related to the same field name across document types have a different field type. |
This worked for me, thanks! |
Works for me, too. Thanks. |
Closing as this should be a non-issue as of 6.0 |
Please solve this issue, the full description is here https://discuss.elastic.co/t/discover-tab-wont-load-anymore/38549/25
This happens when you put
dashboards
andvisualizations
to.kibana
index directly by using ES, not from Kibana UI.Please let Kibana creates
.kibana
index from the scratch with correct mapping for fieldshits
andversion
, so it will looks like this:This is very annoying bug, with this bug the
Discover tab
cannot be loaded.Summary:
When Kibana starts and creates
.kibana
index in ES it didn't put mapping for this index, this is bad for all, who want to put dashboards and visualizations directly in ES, not from Kibana UI.Because when ES sees new type of document without previously setted mapping it try to recognize type of field in this document and here the problem begins. ES recognize type of fields
hits
andversion
likelong
but Kibana needsinteger
type.The text was updated successfully, but these errors were encountered: