[jira] [Comment Edited] (GORA-117) gora hbase does not have a mechanism to set the caching on a scanner, which makes for poor performance on map/reduce jobs

["Alfonso Nishikawa (JIRA)" <ji...@apache.org>]

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

Alfonso Nishikawa edited comment on GORA-117 at 1/3/14 11:59 AM:
-----------------------------------------------------------------

Let's push this, then.

Uploaded proposal GORA-117.patch.
Can anyone check it with goraci? I don't have it configured and I am quite busy to use it for my first time :P
Tests passes without problem, but I don't know if it works as expected.

It adds the option to gora.properties:
{code}
gora.hbasestore.scanner.caching=1000
{code}
with default value 0, and a get/setScannerCaching() to HBaseStore.


was (Author: alfonso.nishikawa):
Let's push this, then.

Uploaded proposal GORA-117.patch.
Can anyone check it with goraci? I don't have it configured and I am quite busy to use it for my first time :P
Tests passes without problem, but I don't know if it works as expected.

It adds the option to gora.properties:
{code}
gora.hbasestore.scanner.caching=1000
{code}
with default value 0.

> gora hbase does not have a mechanism to set the caching on a scanner, which makes for poor performance on map/reduce jobs
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GORA-117
>                 URL: https://issues.apache.org/jira/browse/GORA-117
>             Project: Apache Gora
>          Issue Type: Bug
>          Components: gora-hbase
>    Affects Versions: 0.2
>            Reporter: Eric Newton
>            Assignee: stack
>             Fix For: 0.4
>
>         Attachments: GORA-117.patch
>
>
> goraci runs a map/reduce job over all the data that it generates.  The hbase storage uses a scanner that doesn't cache rows, which means every fetch requires an RPC call.  I experimented with 
> scan.setCaching(1000);
> and goraci Verify ran about 30x faster.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)