[
https://issues.apache.org/jira/browse/HBASE-15410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202319#comment-16202319
]
Josh Elser commented on HBASE-15410:
------------------------------------
bq. I don't expect an optimization as described in the release notes to require
changing test behavior.
That does strike me a bit strange. Looking closer, it looks like these test
cases are actually testing what the hint passed to the filter was. In other
words, it's essentially testing the optimization (not just how users interact
with the Filters).
v3 seems fine to me, but would be nice to wait for [~busbey] to circle back
around since he was also looking at this in HBASE-18957. We don't need to make
more work for each other.
> Utilize the max seek value when all Filters in MUST_PASS_ALL FilterList
> return SEEK_NEXT_USING_HINT
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-15410
> URL: https://issues.apache.org/jira/browse/HBASE-15410
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Labels: filter, perfomance
> Fix For: 1.5.0, 2.0.0-alpha-3, HBASE-18410
>
> Attachments: 15410-wip.patch, 15410.branch-1.patch, 15410.v1.patch,
> 15410.v2.patch, 15410.v3.patch
>
>
> As Preston mentioned in the comment in HBASE-15243:
> https://issues.apache.org/jira/browse/HBASE-15243?focusedCommentId=15143557&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15143557
> An optimization for filters returning a SEEK_NEXT_USING_HINT would be to seek
> to the highest hint (Any previous/lower row won't be accepted by the filter
> returning that seek).
> This JIRA is to explore this potential optimization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
