[ 
https://issues.apache.org/jira/browse/HIVE-14848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903672#comment-15903672
 ] 

Sergio Peña commented on HIVE-14848:
------------------------------------

[~poeppt] Sorry for answering late. I was waiting until we support hadoop 2.9 
in order to use this new variable. I could add it today, but it won't have any 
effect until hadoop 2.9 is released.

Do you think we should have this patch now? Regarding the Tez issue, I don't 
have a Tez engine running to verify it. If you're working on Tez, would you 
like to continue on this patch if you have free time? 

> S3 creds added to a hidden list by HIVE-14588 are not working on MR jobs
> ------------------------------------------------------------------------
>
>                 Key: HIVE-14848
>                 URL: https://issues.apache.org/jira/browse/HIVE-14848
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 2.2.0
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>         Attachments: HIVE-14848.1.patch, HIVE-14848.1.patch
>
>
> When S3 credentials are included in hive-site.xml, then MR jobs that need to 
> read
> data from S3 cannot use them because S3 values are stripped from the Job 
> configuration
> object before submitting the MR job.
> {noformat}
> @Override
> public void initialize(HiveConf conf, QueryPlan queryPlan, DriverContext 
> driverContext) {
>   ...
>   conf.stripHiddenConfigurations(job);
>   this.jobExecHelper = new HadoopJobExecHelper(job, console, this, this);
> }
> {noformat}
> A nice to have (available on hadoop 2.9.0) is an MR 
> {{mapreduce.job.redacted-properties}} that can be used to hide this list on 
> the MR side (such as history server UI) to allow MR run the job without 
> issues.
> UPDATE:
> Change the call to stripHiddenConfigurations() in 
> ql/exec/tez/DagUtils.createConfiguration(), because this is currently broken 
> for running hive-blobstore suite against Tez



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to