[
https://issues.apache.org/jira/browse/PIG-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Graham updated PIG-2174:
-----------------------------
Release Note: Fix HBaseStorage column filtering bug.
Status: Patch Available (was: Open)
> HBaseStorage column filters miss some fields
> --------------------------------------------
>
> Key: PIG-2174
> URL: https://issues.apache.org/jira/browse/PIG-2174
> Project: Pig
> Issue Type: Bug
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2174_1.patch
>
>
> When mixing static and dynamic column mappings, {{HBaseStorage}} sometimes
> doesn't pick up the static column values and nulls are returned. I believe
> this bug has been masked by HBase being a bit over-eager when it comes to
> respecting column filters (i.e. HBase is returning more columns than it
> should).
> For example, this query returns nulls for the {{sc}} column, even when it
> contains data:
> {noformat}
> a = LOAD 'hbase://pigtable_1' USING
> org.apache.pig.backend.hadoop.hbase.HBaseStorage
> ('pig:sc pig:prefixed_col_*','-loadKey') AS
> (rowKey:chararray, sc:chararray, pig_cf_map:map[]);
> {noformat}
> What is very strange (about HBase), is that the same script will return
> values just fine if {{sc}} is instead {{col_a}}, assuming of course that both
> columns contain data:
> {noformat}
> a = LOAD 'hbase://pigtable_1' USING
> org.apache.pig.backend.hadoop.hbase.HBaseStorage
> ('pig:col_a pig:prefixed_col_*','-loadKey') AS
> (rowKey:chararray, col_a:chararray, pig_cf_map:map[]);
> {noformat}
> Potential HBase issues aside, I think there is a bug in the logic on the Pig
> side. Patch to follow.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
