Mapping conflict but no way to resolve anymore

Elastic Stack Kibana
1

In the past, you could click on the conflict field and see which indices are causing the conflict but for some reason you have removed that functionality. Is there some way to see which index is causing the conflict?

Screen Shot 2021-12-21 at 2.02.55 PM
Screen Shot 2021-12-21 at 2.02.55 PM1716×61 3.08 KB

2

Hi, this will be fixed soon

There is a workaround: [Index Patterns] Conflicting fields no longer show matching indices · Issue #114361 · elastic/kibana · GitHub

3

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