You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org> on 2013/02/25 18:58:14 UTC

[jira] [Commented] (PIG-3206) HBaseStorage does not work with Oozie pig action and secure HBase

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

Dmitriy V. Ryaboy commented on PIG-3206:
----------------------------------------

Should we be catching the NoSuchMethodException for all those methods unavailable in 0.92 and 0.20.2? We'll definitely encounter is on m2.invoke in hadoop 0.20.2, according to the comment. 

Looks like now that the Class.forName line moved into an if block, the corresponding ClassNotFoundException should move in there as well.

The description in this JIRA says " it should try and reuse the hbase delegation token in JobConf " if the kerberos token is not available. Where does this reuse happen? I am not sure how this patch solves the problem, but then I don't really know how the kerberos integration in HBaseStorage works in the first place :).

Maybe a test would be helpful?
                
> HBaseStorage does not work with Oozie pig action and secure HBase
> -----------------------------------------------------------------
>
>                 Key: PIG-3206
>                 URL: https://issues.apache.org/jira/browse/PIG-3206
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.10.1
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: 0.12
>
>         Attachments: PIG-3206-1.patch
>
>
> HBaseStorage always tries to fetch delegation token for a secure hbase cluster. But when pig is launched through Oozie, it will fail as TGT is not available in the map job. In that case, it should try and reuse the hbase delegation token in JobConf passed to pig through mapreduce.job.credentials.binary property.

--
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