[GitHub] zeppelin issue #1640: Enable to search interpreters only based on the name

2016-11-18 Thread AhyoungRyu
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1640 @1ambda yeah that could be available approach in the future. Thanks for your review! Then will merge if there are no more discussions. --- If your project is set up for it, you can reply

[GitHub] zeppelin issue #1640: Enable to search interpreters only based on the name

2016-11-17 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1640 @AhyoungRyu If so, i think this is enough. Maybe we need a category dropbox to specify search area later. Thanks for really needed improvement :) --- If your project is set up

[GitHub] zeppelin issue #1640: Enable to search interpreters only based on the name

2016-11-15 Thread AhyoungRyu
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1640 @1ambda Thanks for your suggestion. That would be better I think. Let me update then :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] zeppelin issue #1640: Enable to search interpreters only based on the name

2016-11-15 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1640 I think this PR is cool :) @AhyoungRyu One more question, What do you think if we can filter out interpreters using keywords like `%dep` `%r`? --- If your project is set up for

[GitHub] zeppelin issue #1640: Enable to search interpreters only based on the name

2016-11-15 Thread 1ambda
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/1640 I'v just tested. It works like @AhyoungRyu described. It was annoying before this PR because filter investigated all fields in the interpreter :( - create 2 JDBC interpreter named