[MD] Allow create index patterns for indices with same name but from different datasources.

[kristenTian]

I cannot create an index pattern with an existing name (I should be able to do so, since the data source should be part of the unique ID to disambiguate)

[kristenTian]

Pending tasks:

• The UI validation needs update
• Save Object listing page support
• Visualization creation support
• Discover page support: Prepend <datasource-name>. to index pattern name to differentiate across data sources #2599

Done:

• index pattern DS column support

[kristenTian]

Need to append data source in front of index pattern, pending UX input on:

• Save Object listing page support
• Visualization creation
• Discover page support

[zhongnansu]

@kristenTian is this still on track for 2.5

[kristenTian]

Still pending confirming on the UX look for this task. we can work on it if there is bandwidth.

Base on Kevin and Kroosh, should just be simply pre-append the data source in front of data source everywhere.

[zhongnansu]

Still pending confirming on the UX look for this task. we can work on it if there is bandwidth.

Base on Kevin and Kroosh, should just be simply pre-append the data source in front of data source everywhere.

I am working on this task to allow index-pattern created with same name but different datasources, and there will be some UX/UI changes needed across OSD components where they interact with index patterns. We propose prepending datasource name to index pattern name to distinguish them from UI. E.g. we could display 2 index pattern as datasource-1.index-pattern-name-1 and datasource-2.index-pattern-name-1. See screenshots in reference below for details.

As for the delimiter, I suggest we could use a forbidden character in index-pattern name, for example <>, \, /, instead of .

Based on the previous comment. I'd like to confirm with @kgcreative @KrooshalUX, that we are align on this before I start implementation.

References

1. saved Object listing page:
   
2. visualization creation page:
   
3. Discover Page:
   

cc: @zengyan-amazon @seraphjiang @kristenTian

[joshuarrrr]

@zhongnansu Will this be resolved by #3604?

[zhongnansu]

@zhongnansu Will this be resolved by #3604?

@joshuarrrr yes