-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Index Patterns API - Remove legacy es client usage for field caps #80116
Index Patterns API - Remove legacy es client usage for field caps #80116
Conversation
…ve_legacy_es_client_usage
…:mattkime/kibana into field_caps_remove_legacy_es_client_usage
…legacy_es_client_usage
Pinging @elastic/kibana-app-arch (Team:AppArch) |
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'm rubberstamping this to dismiss the ES-UI codeowner review request triggered by the change to the rollup plugin, butI haven't actually reviewed anything.
Pinging @elastic/apm-ui (Team:apm) |
Pinging @elastic/uptime (Team:uptime) |
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! Tested creating index patterns/refreshing mappings, timelion suggestions. Things seem to be working fine. Looks like some docs need to be updated to pass CI.
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.
Uptime changes LGTM! Tested locally with an alert and all seemed to work.
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.
From KibanaApp team side, there was just the TSVB code fetching fields affected, LGTM, tested locally, works. Also tested to refresh the fields of an index pattern, works. LGTM 👍
rest[1].allowNoIndices = true; | ||
return requestContext.core.elasticsearch.legacy.client.callAsCurrentUser(...rest); | ||
}); | ||
return new IndexPatternsFetcher(requestContext.core.elasticsearch.client.asCurrentUser, true); |
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.
What is true
signifying in this signature? (I assume it's the allowNoIndices
flag based on what was there before but just checking?)
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.
correct!
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.
Thanks! I think my least favorite thing about TS is that it let us all go back to these dangling signatures :P When does GitHub get full TS support??? ;)
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.
Tested locally => LGTM on the security solution!
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 from my previous comments
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…astic#80116) * remove legacy es client usage
Summary
Changing Index Pattern's
IndexPatternFetcher
field fetcher class to use the new es client instead of the legacy client.