hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (Commented) (JIRA)" <>
Subject [jira] [Commented] (HIVE-2764) Obtain delegation tokens for MR jobs in secure hbase setup
Date Tue, 06 Mar 2012 01:19:57 GMT


Enis Soztutar commented on HIVE-2764:

We had some discussion with Ashutosh about how to best approach this. As a part of this issue,
we have to obtain delegation tokens from the storage handler (hbase in this case), and then
pass this to the submitted job. However, HiveStorageHandler.configureTableJobProperties()
does not expose the JobConf object, or an interface to configure the job's credentials. There
seems a couple of options we can go for:
1. At HiveStorageHandler.configureTableJobProperties(), create and save the job credentials
somewhere, and at the time of job submit, merge all the credentials before submitting the
2. Change the HiveStorageHandler.configureTableJobProperties() to get the actual Job to be
submitted, so that Storage handlers have a real shot at configuring the job. 
3. Add a method like HiveStorageHandler.configureJobCredentials(), and call it from HIF.getSplits()
and HiveHBaseTableOutputFormat.checkOutputSpecs(). 

Number 1 and 3 seems hackish, and we will want to give the storagehandlers ability to configure
the actual job. So we are leaning towards that. But this will also be merged with HIVE-2773.
I am still trying to make this work, so any comments / suggestions are more than welcome.

> Obtain delegation tokens for MR jobs in secure hbase setup  
> ------------------------------------------------------------
>                 Key: HIVE-2764
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: HBase Handler, Security
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
> As discussed in HCATALOG-244, in a secure hbase setup with 0.92, we need to obtain delegation
tokens for hbase and save it in jobconf, so that tasks can access region servers. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message