Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1441
@cloverhearts Just tested and checked the code.
Overall same feedbacks as @AhyoungRyu
#### Filtering system
The one you used seems a bit too complicated (also the filter should have
been in a new file).
Since it is also slow, using the same method used in interpreter search
would be better.
#### Filtering input
Try to reuse the same as the interpreter search, it should have the proper
font and keep the same style between pages.
#### Interpreter dropdown filtering
I would remove this feature mainly because it only works with the default
interpreter.
Maybe also remove the default interpreter written on each job?
#### No results
Current message is: `Data does not exist`, `No Job found` would be better
#### Possible future work that could use a Jira issue
* Removing the legend (ready, finished, abort etc...), that info is already
on each dot.
* Make Interpreter and Job page top part fixed, so that we can search even
while scrolling
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
