Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2229
> why is zeppelin.jdbc.auth.kerberos.proxy.enable removed?
My bad, while fixing the above issues, I thought this is redundant, but I
forgot about the case where KERBEROS is enabled and the user does not want to
use proxy behavior. Have reverted that change.
> also is there a way not to hardcode hive jdbc
[here](https://github.com/apache/zeppelin/pull/2229/files#diff-ecdae8ee9594a5c4b21a3c217a3f130cR365)
Hive doesn't work with
[this](https://github.com/apache/zeppelin/pull/2229/files#diff-ecdae8ee9594a5c4b21a3c217a3f130cR370)
(UserGroupInformation.createProxyUser), and since we allow user to configure
multiple JDBC sources using the same interpreter setting; there can be a case
where user has configured say Phoenix (requires
UserGroupInformation.createProxyUser to proxy user) and Hive (fails if
UserGroupInformation.createProxyUser is used), we could introduce new parameter
like `{profile}.kerberos.proxy.enable` but this will increase the documentation
part.
---
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.
---
