[
https://issues.apache.org/jira/browse/HBASE-7772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571794#comment-13571794
]
Gary Helmling commented on HBASE-7772:
--------------------------------------
Based on current evidence, I agree this is not a bug.
I tried to reproduce this with a simple test of HBase token authentication
using current 0.94 branch + Hadoop 1.1.1. (I applied the HBASE-7771 patch to
avoid having to use secure ZK).
The job's task ran successfully and a bit of debugging output I added shows
that the authentication token is being selected correctly by cluster ID.
So there is no problem here that I can see.
> clusterId is not set in conf properly if only
> TableMapReduceUtil.initCredentials() is called
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-7772
> URL: https://issues.apache.org/jira/browse/HBASE-7772
> Project: HBase
> Issue Type: Bug
> Reporter: Francis Liu
> Assignee: Francis Liu
> Fix For: 0.96.0, 0.94.5
>
> Attachments: HBASE-7772_94.patch, HBASE-7772.patch
>
>
> clusterId is not set in the job's conf correctly if only
> TableMapReduceUtil.initCredentials() is called and thus fails to include the
> token when using an hbase client in any of the job's tasks. This is a
> regression.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
