[
https://issues.apache.org/jira/browse/HBASE-15410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zheng Hu updated HBASE-15410:
-----------------------------
Attachment: HBASE-15410.addendum.v1.patch
Seems like I change the seekHintFilters to a HashSet named seekHintFilter after
HBASE-18411. I uploaded the addendum to fix this. Sorry about the noisy.
> 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: 2.0.0-alpha-4, HBASE-18410
>
> Attachments: 15410-wip.patch, 15410.branch-1.patch, 15410.v1.patch,
> 15410.v2.patch, 15410.v3.patch, 15410.v4.patch, HBASE-15410.addendum.v1.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)
