You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (Commented) (JIRA)" <ji...@apache.org> on 2012/03/05 16:45:57 UTC

[jira] [Commented] (HBASE-5517) Region Server Coprocessor : Suggestion for change when next() call with nbRows>1

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

Anoop Sam John commented on HBASE-5517:
---------------------------------------

In HRegionServer next(final long scannerId, int nbRows) 
{code}
for (int i = 0; i < nbRows
          && currentScanResultSize < maxScannerResultSize; i++) {
        requestCount.incrementAndGet();
{code}
Here if next() is called with nbRows=10 we are treating it as 10 requests came to RS. We treat it as 10 different operations on the RS.In that case we better contact the CP 10 times rather than 1 time?  Correct me if I am wrong...:)
                
> Region Server Coprocessor : Suggestion for change when next() call with nbRows>1
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-5517
>                 URL: https://issues.apache.org/jira/browse/HBASE-5517
>             Project: HBase
>          Issue Type: Improvement
>          Components: coprocessors
>    Affects Versions: 0.92.0
>            Reporter: Anoop Sam John
>
> Originated from the discussion under HBASE-2038 [Coprocessor based IHBase]
> Currently preNext() and postNext() will be called once for a next() call into HRegionServer.
> But if the next() is being called with nbRows>1, co processor should provide a chance to do some operation before, after every next() calls into region as part of call next(int scannerId, int nbRows).
> In case of usage of coprocessor with IHBase, before making any calls of next() into a Region, we need to make a reseek() to a row based on the index information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira