[
https://issues.apache.org/jira/browse/HBASE-10018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955057#comment-13955057
]
Nicolas Liochon commented on HBASE-10018:
-----------------------------------------
v5 = v4 rebased + deprecation of getClosestRowOrBefore
getClosestRowOrBefore is actually deprecated in HTableInterface since 0.92: "As
of version 0.92 this method is deprecated without replacement."
But we still use it in a few place, and we can't remove it w/o breaking rolling
upgrades.
> Change the location prefetch
> ----------------------------
>
> Key: HBASE-10018
> URL: https://issues.apache.org/jira/browse/HBASE-10018
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.99.0
>
> Attachments: 10018.v1.patch, 10018.v2.patch, 10018.v4.patch,
> 10018.v5.patch, 10018v3.patch
>
>
> Issues with prefetching are:
> - we do two calls to meta: one for the exact row, one for the prefetch
> - it's done in a lock
> - we take the next 10 regions. Why 10, why the 10 next?
> - is it useful if the table has 100K regions?
> Options are:
> - just remove it
> - replace it with a reverse scan: this would save a call
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
