You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2011/06/17 18:34:47 UTC

[jira] [Commented] (PIG-1870) HBaseStorage doesn't project correctly

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

Harsh J commented on PIG-1870:
------------------------------

Could someone please add the appropriate 0.8.x fix version here? Or if that's done when a release is tagged, np. Just thought it might help those following tickets here :)

> HBaseStorage doesn't project correctly
> --------------------------------------
>
>                 Key: PIG-1870
>                 URL: https://issues.apache.org/jira/browse/PIG-1870
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>            Reporter: Bill Graham
>            Assignee: Dmitriy V. Ryaboy
>             Fix For: 0.9.0
>
>         Attachments: PIG_1870.2.patch, PIG_1870.3.patch, PIG_1870.4.patch, PIG_1870.patch, PIG_1870_1.patch, PIG_1870_for0.8.2.patch, PIG_1870_for0.8.final.patch, PIG_1870_for0.8.patch
>
>
> Projecting columns after {{LOAD}} via {{HBaseStorage}} produces unexpected results. This is related to the {{loadKey}} functionality and how the {{pushProjection}} method in {{HBaseStorage}} has to offset to build a column list that aligns with the tuple (the column list doesn't contain the row key).
> This shift appears to create an inconsistency with the FieldSchema for the tuple which results in the wrong tuple value being fetched for a given column. I'll attach a patch with unit tests that illustrate the problem.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira