-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Lens] Move field existence from Lens to UnifiedFieldList plugin #139453
[Lens] Move field existence from Lens to UnifiedFieldList plugin #139453
Conversation
…eld-existing-to-unified-field-list-plugin # Conflicts: # src/plugins/data_views/public/data_views/data_views_api_client.ts # x-pack/plugins/lens/public/app_plugin/app.tsx # x-pack/plugins/lens/public/indexpattern_service/loader.ts # x-pack/plugins/lens/public/indexpattern_service/service.ts # x-pack/plugins/lens/public/mocks/data_views_service_mock.ts # x-pack/plugins/lens/server/plugin.tsx # x-pack/plugins/lens/server/routes/existing_fields.ts
@elasticmachine merge upstream |
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
@elasticmachine merge upstream |
@@ -7,3 +7,4 @@ | |||
*/ | |||
|
|||
export const PLUGIN_ID = 'unifiedFieldList'; | |||
export const FIELD_EXISTENCE_SETTING = 'unifiedFieldList:useFieldExistenceSampling'; |
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 think need migration from lens:useFieldExistenceSampling
to unifiedFieldList:useFieldExistenceSampling
, else the previous value of unifiedFieldList:useFieldExistenceSampling
will get lost
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.
Didn't run but looks good except for the renaming of the advanced setting, I don't think that's worth the effort.
@@ -367,7 +367,9 @@ function FieldItemPopoverContents(props: FieldItemProps) { | |||
} | |||
|
|||
if (params?.noDataFound) { | |||
const isUsingSampling = core.uiSettings.get('lens:useFieldExistenceSampling'); | |||
const isUsingSampling = core.uiSettings.get( | |||
'unifiedFieldList:useFieldExistenceSampling' |
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 change is not backwards compatible. As we are going to remove this setting in 8.6 anyway, let's keep it under the old name.
@dimaanj can the draft status be removed on this for final review? |
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 and Lens integration works fine, LGTM
@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.
app services changes LGTM
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 did just a quick check of the code and functionality locally in Lens, LGTM! Thx for taking care of this! 👍
@elasticmachine merge upstream |
merge conflict between base and head |
…eld-existing-to-unified-field-list-plugin
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
History
To update your PR or re-run it, just comment with: cc @dimaanj |
Summary
Closes #137658
This PR moves field existence API from Lens server to a common area of UnifiedFieldList plugin. There should be no UI changes.
Checklist