GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/1979
[ZEPPELIN-2063] Hive Jdbc interpreter does not relogin if kerberos ticket
expired when hive.server2.transport.mode is http
### What is this PR for?
Hadoop Client will re-login once the ticket expired in case of RPC and so
when hive.server2.transport.mode is binary, Hive Jdbc interpreter does a
relogin and works fine. But when Rest API is used i.e when
hive.server2.transport.mode is http, it is not doing a re-login and so fails
with GSS exception.
### What type of PR is it?
[Bug Fix]
### What is the Jira issue?
* [ZEPPELIN-2063](https://issues.apache.org/jira/browse/ZEPPELIN-2063)
### How should this be tested?
Run hive in http mode i.e. hive.server2.transport.mode is http. Run any
query say `show tables` now wait for key to expire (usually its 24hrs), now try
to run the same paragraph again without restarting zeppelin-server or jdbc
interpreter. It should not fail with `GSSException: No valid credentials
provided (Mechanism level: Failed to find any Kerberos tgt)
` exception
### Screenshots (if appropriate)
N/A
### Questions:
* Does the licenses files need update? N/A
* Is there breaking changes for older versions? N/A
* Does this needs documentation? N/A
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-2063
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1979.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1979
----
commit 40e14c4c0b7aa7c1201b4eaa2af661be111c0c98
Author: Prabhjyot Singh <[email protected]>
Date: 2017-02-06T12:54:34Z
try to re login from keytab before failing.
----
---
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.
---
