hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chunhui shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6870) HTable#coprocessorExec always scan the whole table
Date Wed, 26 Sep 2012 02:04:07 GMT

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

chunhui shen commented on HBASE-6870:
-------------------------------------

[~v.himanshu]
These two if statements is not made by this patch, so I just keep the previous.

{code}
public LinkedHashMap<byte[], HRegionLocation> getKeysToRegionsInRange(
{code}

Yes, it could be private.

Thanks for the review.

I will rework patch with other comments later
                
> HTable#coprocessorExec always scan the whole table 
> ---------------------------------------------------
>
>                 Key: HBASE-6870
>                 URL: https://issues.apache.org/jira/browse/HBASE-6870
>             Project: HBase
>          Issue Type: Improvement
>          Components: Coprocessors
>    Affects Versions: 0.94.1
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: HBASE-6870.patch, HBASE-6870-testPerformance.patch, HBASE-6870v2.patch,
HBASE-6870v3.patch
>
>
> In current logic, HTable#coprocessorExec always scan the whole table, its efficiency
is low and will affect the Regionserver carrying .META. under large coprocessorExec requests

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message