[
https://issues.apache.org/jira/browse/PIG-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016001#comment-13016001
]
Dmitriy V. Ryaboy commented on PIG-1870:
----------------------------------------
The problem isn't loadKey, it's that we set up a (static) TableInputFormat.SCAN
in setLocation, which gets called multiple times, and not always after
pushProjection; we wind up overwriting SCAN and "forgetting" we are pushing
things. I am working on a patch.
> 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
> Attachments: PIG_1870_1.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
