You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Nick Pinckernell (JIRA)" <ji...@apache.org> on 2012/09/27 05:37:07 UTC

[jira] [Commented] (PIG-2615) HBase region observer coprocessor not firing from Pig 'store'

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

Nick Pinckernell commented on PIG-2615:
---------------------------------------

Here is the conversation that was had at the HBase forum:
http://mail-archives.apache.org/mod_mbox/hbase-user/201203.mbox/%3CCABsY1jQ8+OiLh7SYkXZ8iO=NosY8khz7iYs+6W4u6SxCpJ5s9g@mail.gmail.com%3E

For pig 0.9.2 the issue looked like when pig was invoking the put.add() method in the HBaseStorage class that the ts that was being passed was incorrect and the coprocessor would not fire for those rows with that version of the 'ts' could not be found.  I have not checked pig 0.10.0 yet.

                
> HBase region observer coprocessor not firing from Pig 'store'
> -------------------------------------------------------------
>
>                 Key: PIG-2615
>                 URL: https://issues.apache.org/jira/browse/PIG-2615
>             Project: Pig
>          Issue Type: Bug
>          Components: data
>    Affects Versions: 0.9.2
>         Environment: Pig 0.9.2, HBase 0.92, Hadoop 1.0.0
>            Reporter: Nick Pinckernell
>            Assignee: Nick Pinckernell
>            Priority: Minor
>              Labels: hbase, newbie, patch
>         Attachments: HBaseStorage_java_coprocessor.patch
>
>
> When using pig to load data into HBase the region observer coprocessor (specifically prePut() as I have not tested all the other possible region observer combinations) with the 'store' command the coprocessor is not getting invoked.
> I have tracked this down and come up with a simple patch.  A record of the investigation is on both the Pig and HBase user forums.

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