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

Robert Kanter updated OOZIE-1646:
---------------------------------

    Attachment: OOZIE-1646.patch

There's actually another tiny change that had to be made to get this to work 
properly for two HBases; new patch has this change.  

The problem was that HbaseCredentials is merging the action's config, the hbase 
config, and the credential's config in a particular way.  Before, if a property 
was already defined in the action's config, the credential's config wouldn't 
override it when getting the token.  So, if the property 
{{hbase.zookeeper.quorum}} is specified in both credentials to different HBases 
(to acquire tokens for each HBase) and is also set to the first HBase in the 
action's config, then when trying to acquire the tokens, it was getting both of 
them from the first HBase because it wouldn't override the action's 
{{hbase.zookeeper.quorum}} with the credential's {{hbase.zookeeper.quorum}}.  

Special thanks to [~cconner] for help testing this.

> HBase Table Copy between two HBase servers doesn't work with Kerberos
> ---------------------------------------------------------------------
>
>                 Key: OOZIE-1646
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1646
>             Project: Oozie
>          Issue Type: Improvement
>          Components: action, security
>    Affects Versions: 3.3.2, 4.0.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: OOZIE-1646.patch, OOZIE-1646.patch, OOZIE-1646.patch
>
>
> If you try to use the Java action to do an HBase copy between two HBase 
> servers with Kerberos, it will fail.  We need to update the 
> {{HbaseCredentials}} to support acquiring *two* HBase delegation tokens.  
> We should also update the documentation to mention that multiple credentials 
> can be used by the same action (e.g. {{cred="foo,bar"}}).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to