Why does the mapping of Kibana index change after 6.0

(Steven Zhao) #1

previously I got a problem. and I posted it in Elastic forum.

"I used python to import/export index-pattern and other saved objects automatically. Even there were some changes in each version, but mostly the script worked fine. However, in Elastic 6.1 (es and kibana), after I imported all those to ElasticSearch, I found Kibana could not display index-pattern, even all data was ingested in ".kibana" index. Kibana requested a new index pattern creation. But if I imported some data and created an index pattern in Kibana manually, then ran script to import all, everything was back. and I can remove sample index-pattern and view dashboard or visualization. I compared the ".kibana" index for both scenario, hardly pointing out where was different. Someone can help on this case? Or could someone tell me what are changes between Kibana 6.0 and 6.1?"

finally I realized the issue was because of Kibana mapping. The mapping of ".kibana" has changed between 6.0 and 6.1.
Can anyone tell me the further impact if we still use the mapping of 6.0 version please?

(Tyler Smalley) #2

If you're wanting to programmatically update the data persisted by Kibana I would suggest using the API outlined in this pull request: https://github.com/elastic/kibana/pull/11632

The mapping and underlying data structure can change, so this API will provide consistency between versions.

(system) #3

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