-
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
[Maps] move apply global filter settting from layer to source #50523
[Maps] move apply global filter settting from layer to source #50523
Conversation
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
Pinging @elastic/kibana-gis (Team:Geo) |
Pinging @elastic/kibana-docs (Team:Docs) |
@spong I added you as a review since this PR touches the layer definitions in SIEM. Would you mind reviewing the SIEM changes? |
💔 Build Failed |
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.
SIEM changes LGTM -- thanks @nreese!
💔 Build Failed |
💚 Build Succeeded |
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.
Great PR.
This was flagged during this PR, although not directly related:
wrt
Line 46 in 0cd9d6c
const indexPatternIds = this.props.layer.getIndexPatternIds(); |
After discussion, we decided to change this to getSourceIndexPatterns
. The filter should only apply to the source-data, not any of the term-joins. That is actually the current behavior, and documented like this (https://www.elastic.co/guide/en/kibana/7.x/maps-layer-based-filtering.html). The UX shouldn't include auto-complete for any of the join-indices, as that wouldn't function anyway.
...legacy/plugins/maps/public/connected_components/layer_panel/layer_settings/layer_settings.js
Show resolved
Hide resolved
x-pack/legacy/plugins/maps/public/layers/sources/client_file_source/geojson_file_source.js
Show resolved
Hide resolved
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.
Docs LGTM
💔 Build Failed |
💚 Build Succeeded |
…c#50523) * [Maps] move apply global filter settting from layer to source * add checkbox to join UI * update edit UI for grid and pew-pew source * add migrations * update docs * remove setting of applyGlobalQuery from geojson upload * upgrade SIEM layer descriptors * fix jest tests and api integration tests * fix functional tests * fix functional test * i18n * review feedback * doc re-wording * i18n fixes
…-fallback * 'master' of github.com:elastic/kibana: (116 commits) [Maps] move apply global filter settting from layer to source (elastic#50523) [SIEM] Fix: Empty `Source` / `Destination` shown when only ports are populated (elastic#50843) [Maps] Delay vector tile layer syncing until spritesheet is loaded (elastic#48955) [Maps] prevent users from overflowing URL when filtering by shape (elastic#50747) [DOCS] Mark Beats central management as discontinued (elastic#49423) [page_objects/common_page] convert to ts (elastic#50771) [NP Kibana Migrations ] kibana plugin home (elastic#50444) [DOCS] Shareables naming convention (elastic#50497) [ML] DF Analytics - auto-populate model_memory_limit (elastic#50714) Increase alerting test stability and reduce flakiness (elastic#50246) [ML] Remaning new_job_new folder (elastic#50917) [Telemetry] Show opt-in changes for OSS users (elastic#50831) [ML] Fix lat_long anomalies table links menu and value formatting (elastic#50916) [Dev] Fix serialising a really big string (elastic#50915) Better explanation about the Prettier recommendation (extension vs. NPM module) (elastic#50629) [Monitoring] Use a basic monitoring user for tests (elastic#47865) [Monitoring] Gracefully handle issue with filebeat indices (elastic#48929) [Monitoring] Improve permissions required around setup mode (elastic#50421) Additional validation for elasticsearch username (elastic#48247) Revert changes to use_kibana_ui_setting (elastic#50877) ... # Conflicts: # src/legacy/core_plugins/console/server/request.test.ts
#50972) * [Maps] move apply global filter settting from layer to source * add checkbox to join UI * update edit UI for grid and pew-pew source * add migrations * update docs * remove setting of applyGlobalQuery from geojson upload * upgrade SIEM layer descriptors * fix jest tests and api integration tests * fix functional tests * fix functional test * i18n * review feedback * doc re-wording * i18n fixes
fixes #43849
This PR moves
applyGlobalQuery
from the layer descriptor to the source descriptor. That way, you can enable/disable global query context for the source or each join independently.This PR also effects GeoJson upload.
applyGlobalQuery
is no longer defaulted false for GeoJson upload layers.To test this PR you need to have a document index in ES that can be joined with another document index in ES. The get-it-done data set along with San Diego council districts provides a good example where you want to filter the join source by get-it-done data set but want to avoid filtering the council district polygons by global search criteria. Follow the instructions at https://github.com/nreese/presentations/tree/master/get_it_done to load get_it_done data set and council district geojson.