You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Dave Latham (JIRA)" <ji...@apache.org> on 2013/12/02 18:42:36 UTC

[jira] [Commented] (HBASE-9931) Optional setBatch for CopyTable to copy large rows in batches

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

Dave Latham commented on HBASE-9931:
------------------------------------

The patch adds setBatch and removes setCaching.   I think setCaching should stay in there too - probably a copy/replace bug?

> Optional setBatch for CopyTable to copy large rows in batches
> -------------------------------------------------------------
>
>                 Key: HBASE-9931
>                 URL: https://issues.apache.org/jira/browse/HBASE-9931
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>            Reporter: Dave Latham
>         Attachments: HBASE-9931.00.patch
>
>
> We've had CopyTable jobs fail because a small number of rows are wide enough to not fit into memory.  If we could specify the batch size for CopyTable scans that shoud be able to break those large rows up into multiple iterations to save the heap.



--
This message was sent by Atlassian JIRA
(v6.1#6144)