You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:37:44 UTC

[jira] [Resolved] (SPARK-14276) Allow each HiveContext to have distinct users that they will use to connect to the HiveMetastore

     [ https://issues.apache.org/jira/browse/SPARK-14276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon resolved SPARK-14276.
----------------------------------
    Resolution: Incomplete

> Allow each HiveContext to have distinct users that they will use to connect to the HiveMetastore
> ------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-14276
>                 URL: https://issues.apache.org/jira/browse/SPARK-14276
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Alex Forbes
>            Priority: Minor
>              Labels: Authentication, Authorization, Hive, HiveMetaStoreClient, SQL, bulk-closed
>
> Currently the HiveContexts use the UserGroupInformation to determine which user to connect to the HiveMetastore.
> This is either determined from an Environment variable, the user that is running the spark process, or a static user.
> With Spark 1.6 there was the introduction of multiple HiveContext Sessions but each session uses the same HiveClient which uses the same user.
> We would like access to specify which user to connect to the Hive Metastore for each HiveContext so that it will integrate better with our Authentication and Authorization mechanisms.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org