You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2015/09/22 01:05:05 UTC
[jira] [Updated] (PIG-4663) HBaseStorage should allow the
MaxResultsPerColumnFamily limit to avoid memory or scan timeout issues
[ https://issues.apache.org/jira/browse/PIG-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohini Palaniswamy updated PIG-4663:
------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
+1. Committed to trunk. Thanks for the contribution [~pmazak]
> HBaseStorage should allow the MaxResultsPerColumnFamily limit to avoid memory or scan timeout issues
> ----------------------------------------------------------------------------------------------------
>
> Key: PIG-4663
> URL: https://issues.apache.org/jira/browse/PIG-4663
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.12.0
> Reporter: Paul Mazak
> Assignee: Paul Mazak
> Attachments: PIG-4663.patch
>
>
> The HBase client Scan API offers a way to setMaxResultsPerColumnFamily. This number prevents all the columns from being consumed when scanning a row. If you have a single row with several thousand columns on it, Pig will likely fail giving an OutOfMemoryException or ScannerTimeoutException.
> The suggestion is to add the option '-maxResultsPerColumnFamily' which can be passed as an optString parameter in the constructor, which sets this value on the HBase Scan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)