GitHub user yaooqinn opened a pull request:

    https://github.com/apache/spark/pull/17333

    [SPARK-19997] [SQL]fix proxy ugi could not get tgt to cause metastore 
connecting problem

    ## What changes were proposed in this pull request?
    
    Pass the real user ugi instead of proxy ugi for hive metastore client to 
find right Kerberos tgt
    
    ## How was this patch tested?
    
    manually
    
    before
     ```
    17/03/17 16:05:41 INFO hive.metastore: Trying to connect to metastore with 
URI thrift://xxxxxx:9083
    17/03/17 16:05:41 ERROR transport.TSaslTransport: SASL negotiation failure
    javax.security.sasl.SaslException: GSS initiate failed [Caused by 
GSSException: No valid credentials provided (Mechanism level: Failed to find 
any Kerberos tgt)]
    ```
    after
    ```java
    17/03/17 17:27:48 INFO hive.metastore: Trying to connect to metastore with 
URI thrift://xxxxxxxx:9083
    17/03/17 17:27:48 INFO hive.metastore: Connected to metastore.
    ```
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yaooqinn/spark proxy-metastore

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/17333.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 #17333
    
----
commit 55109d9f7aa0443dff53877e84b9705ef3566067
Author: Kent Yao <[email protected]>
Date:   2017-03-17T09:16:17Z

    fix proxy ugi could not get tgt to cause metastore connecting problem

----


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to