GitHub user 1ambda reopened a pull request:

    https://github.com/apache/zeppelin/pull/2324

    [ZEPPELIN-2512] Prevent slow note, interpreter search. (master, branch-0.7)

    ### What is this PR for?
    
    Use debounce in search input to avoid the slow search.
    
    See more:
    
    
![image](https://cloud.githubusercontent.com/assets/4968473/25814653/3be8890e-3459-11e7-9be2-6a440ab41861.png)
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    
    NONE
    
    ### What is the Jira issue?
    
    [ZEPPELIN-2512](https://issues.apache.org/jira/browse/ZEPPELIN-2512)
    
    ### How should this be tested?
    
    1. Create many notes with different names. (50+)
    2. Search using note name filter in home and navbar.
    3. Do the same thing for interpreters in the interpreter page
    
    ### Screenshots (if appropriate)
    
    NONE
    
    ### Questions:
    * Does the licenses files need update? - NO
    * Is there breaking changes for older versions? - NO
    * Does this needs documentation? - NO


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/1ambda/zeppelin 
ZEPPELIN-2512/add-debounce-for-search-inputs

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2324.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2324
    
----
commit 7a4446e72965c46ea11900c57b3032cc657f9fcb
Author: 1ambda <1am...@gmail.com>
Date:   2017-05-08T16:32:55Z

    feat: Add debounce for note name filter

commit 8730614a1c9df622e756b77cbc29f7eda550b85e
Author: 1ambda <1am...@gmail.com>
Date:   2017-05-08T16:35:38Z

    feat: Add debounce for interpreter search input

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to