Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1441
  
    @AhyoungRyu @corneadoug 
    Thank you very much for your feedback.
    
    #### Filtering system
    I think the filter I added here actually will improve filtering performance 
since as soon as you press return key, it will show filtering result. And if 
there is no input from user for more than 2 sec, it stops filtering.
    
    The reason I implemented filtering myself is to fix the latency issue with 
large number of notebooks. If you filter on every keydown event, it will freeze 
browser when you have a lot of notebooks.(tested with 250 notebooks). 
    
    Will it be better if I add UI letting user know that they should press 
return button to complete filtering?
    
    
    @corneadoug 
    actually, I've used the interpreter filtering in the first implementation.
    However, the behavior is a bit different from job filtering. So I had to 
define separate filters.
    
    #### Filtering input and No results
    Your opinion is right.
    Okay, I will fix it.
    
    #### Interpreter dropdown filtering
    I think this feature is very important.
    because currently there is no way to manage your interpreter which are not 
bound to notebook.
    also, if you use a lot of notebooks and interpreter, I think users would 
want to see and sort it.
    Personally I also wanted to have this kind of view when i was using cron 
scheduler to operating a notebook then can not find problem for interpreter 
bind.
    I think this feature is a good way to be feedback to the user.
    
    #### Possible future work that could use a jira issue
    Yes, I agree with your opinion.
    i will make a jira issue and implement those in future.
    
    Thank you again.


---
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