Skip to content
This repository has been archived by the owner on Oct 30, 2021. It is now read-only.

enable saved search selection filtering #100

Merged
merged 2 commits into from
Feb 1, 2017

Conversation

nreese
Copy link
Contributor

@nreese nreese commented Dec 30, 2016

Adds an input to the kibiSelectPort directive. The value of this input is used to query saved searches. When the value changes, an elasticsearch/.kibana/search/_search?size=100 request is sent to the server to request saved searches containing the input value in either the title or description.

The ability to filter saved searches allows users to select saved searches once the kibana index exceeds 100 saved searches as defined in issue #99. The ability to filter saved searches also allows users to easily find a saved search as the selection list gets longer.

image

close #99

@jccq
Copy link

jccq commented Dec 30, 2016 via email

@scampi
Copy link
Contributor

scampi commented Jan 3, 2017

The ability to filter saved searches allows users to select saved searches once the kibana index exceeds 100 saved searches as defined in issue #99.

@nreese Can you further describe what would be the interaction ? You save each search with a different time range ?

@sindicetech-jenkins
Copy link

Can one of the admins verify this patch?

@szydan
Copy link
Contributor

szydan commented Jan 5, 2017

jenkins test it

@szydan
Copy link
Contributor

szydan commented Jan 5, 2017

@nreese please rebase on master as there is 1 test failing (it was already fixed on master)

@nreese nreese force-pushed the filterSavedSearches branch from 8484b1c to efb2e79 Compare January 6, 2017 01:12
@nreese
Copy link
Contributor Author

nreese commented Jan 6, 2017

@scampi Imagine a kibana instance with 120 saved searches. In the current implementation, the Saved Search id select only shows the first 100 saved searches. How would a user select one of the other 20 saved searches since they do not appear in the selection list? This feature provides a mechanism to solve that problem. When the page is first viewed, the filter is empty and a query returns the first 100 saved searches. A user could then enter text into the filter box. This will trigger another query to re-populate the Saved Search id selection list with saved searches that match the filter text. There are no time ranges involved.

@scampi
Copy link
Contributor

scampi commented Jan 10, 2017

@nreese I misunderstood what this PR tries to fix, now it's clear, thanks

@@ -6,6 +6,8 @@ define(function (require) {
config, $http, courier, indexPatterns, timefilter, Private, Promise, kbnIndex
) {

const searchService = Private(require('ui/saved_objects/saved_object_registry')).byLoaderPropertiesName.searches;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add savedSearches to the argument list above and remove this.

@CLAassistant
Copy link

CLAassistant commented Jan 20, 2017

CLA assistant check
All committers have signed the CLA.

@nreese
Copy link
Contributor Author

nreese commented Jan 20, 2017

Why is CLAassistant flagging me for not signing a CLA? I signed one a couple of months ago

@scampi
Copy link
Contributor

scampi commented Jan 23, 2017

@nreese we moved to this new CLA tool that is easily integrated with github. Although it is the same agreement as before, could you accept it one more time ? thanks.

@szydan
Copy link
Contributor

szydan commented Jan 27, 2017

jenkins test it

@scampi scampi merged commit 0e69f0c into sirensolutions:master Feb 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Saved search select only shows first 100 saved searches.
6 participants