[
https://issues.apache.org/jira/browse/HBASE-7772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571629#comment-13571629
]
Gary Helmling commented on HBASE-7772:
--------------------------------------
I'm not sure I understand the underlying issue here. Cluster ID should come
from the cluster that SecureClient is connecting to, which will be driven by
the zookeeper quorum configuration. The Token instance obtained and stored in
the job's credentials should also have the cluster ID set. So I'm not
following why the cluster ID needs to be set in the job conf?
It's entirely possible that HBASE-7442 or HBASE-7626 broke some part of how
this ties together. Can you describe where in the flow the correct cluster ID
is not being found, though?
> 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
