Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1364
Thanks @AhyoungRyu , I have added `bigquery` in the following commit.
BTW, I don't this is a good idea to define the interpreter order in this
way. Because it brings extra overhead when adding new interpreter. And I think
it will break when we have multiple interpreter setting for the same
interpreter (e.g. 2 interpreter setting for spark, one for spark1, another for
spark2).
So I am thinking that maybe we can allow user to define the ordering in the
interpreter page, the available interpreter can be fetched through rest api. So
that we won't miss any interpreter when new interpreter is added. \cc
@Leemoonsoo @jongyoul
---
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.
---
