Mapping conflict but no way to resolve anymore

seanziee · December 21, 2021, 10:13pm

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?

dosant · December 22, 2021, 10:56am

Hi, this will be fixed soon

github.com/elastic/kibana

[Index Patterns] Conflicting fields no longer show matching indices

opened 09:09PM - 07 Oct 21 UTC

closed 05:28PM - 11 Nov 21 UTC

TheRiffRafi

bug loe:hours Team:AppServicesSv impact:low

**Kibana version:** 7.15.0 **Elasticsearch version:** 7.15.0 **Describe th…e bug:** This was requested back in: https://github.com/elastic/kibana/issues/45135 It looks like it was implemented as it was working on 7.12.1: <img width="1240" alt="Screen Shot 2021-10-07 at 16 07 14" src="https://user-images.githubusercontent.com/62263912/136462365-d2b21d54-9b84-4b6c-90cc-80df93a8d11c.png"> And now looking at 7.15 we see that conflicting indices are no longer showing up: <img width="1492" alt="Screen Shot 2021-10-07 at 16 08 14" src="https://user-images.githubusercontent.com/62263912/136462479-905cc7ef-9107-4f26-9bc2-1b55faff95f7.png"> **Expected behavior:** Clicking on field should show conflicting indices.

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

system · January 19, 2022, 10:56am

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