You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Dávid Paksy (Jira)" <ji...@apache.org> on 2024/11/06 08:41:00 UTC

[jira] [Commented] (HBASE-28621) PrefixFilter should use SEEK_NEXT_USING_HINT

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

Dávid Paksy commented on HBASE-28621:
-------------------------------------

Many thanks for the reviews [~stoty]. 

> PrefixFilter should use SEEK_NEXT_USING_HINT 
> ---------------------------------------------
>
>                 Key: HBASE-28621
>                 URL: https://issues.apache.org/jira/browse/HBASE-28621
>             Project: HBase
>          Issue Type: Improvement
>          Components: Filters
>            Reporter: Istvan Toth
>            Assignee: Dávid Paksy
>            Priority: Major
>              Labels: beginner, beginner-friendly, pull-request-available
>             Fix For: 2.7.0, 3.0.0-beta-2, 2.5.11, 2.6.2
>
>
> Looking at PrefixFilter, I have noticed that it doesn't use the SEEK_NEXT_USING_HINT mechanism.
> AFAICT, we could safely set the the prefix as a next row hint, which could be a huge performance win.
> Of course, ideally the user would set the scan startRow to the prefix, which avoids the problem, but the user may forget to do that, or may use the filter in a filterList that doesn't allow for setting the start/stop rows close tho the prefix.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)