-
Notifications
You must be signed in to change notification settings - Fork 914
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
Prepend <datasource-name>.
to index pattern name to differentiate across data sources
#2599
Comments
does it mean when we create a index pattern with data source ,and we want to name is "ds-1". After creation, what actually saved in the index is with name field |
datasource.
to the index pattern name to help users differentiate between data sourcesdatasource.
to the index pattern name to help users differentiate between data sources in Discover
I don't think so, it should be a UI tweak in Discover app, after the UX review meeting, let's decide which phase this feature is needed. |
@kristenTian Is MD not transparent to the applications? Will each plugin need to be modified to support MD? |
Synced offline. In short, for plugin leveraging data plugin search client will be transparent. |
@kristenTian is this still on track for 2.5? |
Will this be enough? Or did we want to maybe to try some A/B testing to verify if this will help our users differentiate? |
This is the related task: #2597 (comment). Basically the following components are involved:
This can definitely be helpful to users when there are duplicated index pattern names. |
@kristenTian Assigning to you, as it appears you have the parent task assigned. |
bumped release target to |
datasource.
to the index pattern name to help users differentiate between data sources in Discover<datasource-name>.
to index pattern name to differentiate across data sources
closing this to avoid confusion, as there's another issue #3604 opened to track the same issue |
In Discover, Prepend datasource. to the index pattern name to help users differentiate between data sources
The text was updated successfully, but these errors were encountered: