hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15410) Utilize the max seek value when all Filters in MUST_PASS_ALL FilterList return SEEK_NEXT_USING_HINT
Date Wed, 06 Sep 2017 15:58:00 GMT

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

Chia-Ping Tsai commented on HBASE-15410:
----------------------------------------

{code}
+  private Set<Filter> seekHintFilter = new HashSet<>();
{code}
Why use HashSet rather than List?

> 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
>         Attachments: 15410.v1.patch, 15410.v2.patch, 15410-wip.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)

Mime
View raw message