-
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
Adding filter pills causes double fetch in discover and dashboards #54887
Labels
Comments
Pinging @elastic/kibana-app-arch (Team:AppArch) |
7 tasks
lizozom
pushed a commit
to lizozom/kibana
that referenced
this issue
Jan 19, 2020
- Filters are not only fetch once on timefilter change - Make sure that discover doesn't fetch data when a disabled filter is changed - Support compareFilters on an array of filters. - Added tests to compare filters - Exctracted sortFilters and added tests to it.
7 tasks
lizozom
pushed a commit
that referenced
this issue
Jan 21, 2020
* Fix bug #54887 - Filters are not only fetch once on timefilter change - Make sure that discover doesn't fetch data when a disabled filter is changed - Support compareFilters on an array of filters. - Added tests to compare filters - Exctracted sortFilters and added tests to it. * code review + FilterCompareOptions * Remove sort by Co-authored-by: Elastic Machine <[email protected]>
lizozom
pushed a commit
to lizozom/kibana
that referenced
this issue
Jan 21, 2020
* Fix bug elastic#54887 - Filters are not only fetch once on timefilter change - Make sure that discover doesn't fetch data when a disabled filter is changed - Support compareFilters on an array of filters. - Added tests to compare filters - Exctracted sortFilters and added tests to it. * code review + FilterCompareOptions * Remove sort by Co-authored-by: Elastic Machine <[email protected]>
lizozom
pushed a commit
to lizozom/kibana
that referenced
this issue
Jan 21, 2020
* Fix bug elastic#54887 - Filters are not only fetch once on timefilter change - Make sure that discover doesn't fetch data when a disabled filter is changed - Support compareFilters on an array of filters. - Added tests to compare filters - Exctracted sortFilters and added tests to it. * code review + FilterCompareOptions * Remove sort by Co-authored-by: Elastic Machine <[email protected]>
lizozom
pushed a commit
that referenced
this issue
Jan 21, 2020
) * Fix bug #54887 - Filters are not only fetch once on timefilter change - Make sure that discover doesn't fetch data when a disabled filter is changed - Support compareFilters on an array of filters. - Added tests to compare filters - Exctracted sortFilters and added tests to it. * code review + FilterCompareOptions * Remove sort by Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
lizozom
pushed a commit
that referenced
this issue
Jan 21, 2020
) * Fix bug #54887 - Filters are not only fetch once on timefilter change - Make sure that discover doesn't fetch data when a disabled filter is changed - Support compareFilters on an array of filters. - Added tests to compare filters - Exctracted sortFilters and added tests to it. * code review + FilterCompareOptions * Remove sort by Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
@lizozom @flash1293 can this be closed? |
Yep, can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Kibana version: master
Elasticsearch version:
Server OS version:
Browser version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
src/plugins/data/public/query/filter_manager/lib/mappers/map_phrase.ts
adds a formatter function to the filter object. However the filter in theappState
won't have this property. This causes the filter manager to trigger subscribers to fetch because thefilter_manager
checks equality by a simple deep equality check: https://github.com/elastic/kibana/blob/master/src/plugins/data/public/query/filter_manager/filter_manager.ts#L92It looks like the same thing is also happening in dashboards.
In case of discover this causes
fetch
to be called two times:setFilters
, which causes the first fetch to be dispatchedvalue
(maybe because it gets deserialized from the url?), but the filterManager one has.Steps to reproduce:
Expected behavior:
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: