[
https://issues.apache.org/jira/browse/HBASE-6870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624599#comment-13624599
]
chunhui shen commented on HBASE-6870:
-------------------------------------
bq.How come useCache being true gets translated into includeEndKey being true ?
The useCache flag is not related with includeEndKey, includeEndKey is always
true in HTable#coprocessorService.
bq.I wonder if we should provide a mechanism for coprocessors to specify
whether fresh .META. scan is wanted.
Making a useCache flag is used for performance comparision in my initial
purpose, I think there's no necessary to provide a choice for fresh .META. scan
since it is still able to get a invalid region location from the .META.
> 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, 0.95.0, 0.95.2
> Reporter: chunhui shen
> Assignee: chunhui shen
> Priority: Critical
> Fix For: 0.95.1, 0.98.0
>
> Attachments: 6870-v4.txt, HBASE-6870.patch,
> HBASE-6870-testPerformance.patch, HBASE-6870v2.patch, HBASE-6870v3.patch,
> hbase-6870v5.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
