-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Discover] Rename Index pattern to Data view #110402
[Discover] Rename Index pattern to Data view #110402
Conversation
# Conflicts: # src/plugins/discover/public/application/components/doc/doc.tsx # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -98,7 +98,7 @@ export function Doc(props: DocProps) { | |||
<EuiLink href={indexExistsLink} target="_blank"> | |||
<FormattedMessage | |||
id="discover.doc.somethingWentWrongDescriptionAddon" | |||
defaultMessage="Please ensure the index exists." | |||
defaultMessage="Please ensure the data view exists." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is referring to ES index and should not be renamed.
@@ -107,8 +107,8 @@ export function resolveIndexPattern( | |||
} | |||
|
|||
if (stateVal && !stateValFound) { | |||
const warningTitle = i18n.translate('discover.valueIsNotConfiguredIndexPatternIDWarningTitle', { | |||
defaultMessage: '{stateVal} is not a configured index pattern ID', | |||
const warningTitle = i18n.translate('discover.valueIsNotConfiguredDataViewIDWarningTitle', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should be changing the keys just yet. I would leave this for a code-cleanup phase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it's fine as in other renaming PRs keys were updated too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree with Dziana here, let's keep it as it
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
43a1f38
to
f22e5f9
Compare
…h' into discover-index-pattern-to-data-view
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
d393aeb
into
elastic:index_patterns_to_data_views_user_content_feature_branch
Part of #114083
Summary
Renamed
index patterns
todata views
in Discover UI.Checklist
For maintainers