[
https://issues.apache.org/jira/browse/HBASE-15410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332391#comment-15332391
]
Jeff Zhang commented on HBASE-15410:
------------------------------------
I did some testing against Ted's patch and was able to reproduce the error he
mentioned above.
I think the error was due to FilterList being unable to reset the
"seekHintFilter" set until nextRow() is called which effectively led the scan
to a standstill if the max seek value returned points to the current row (i.e.
column filter) which in turn caused the client timeout.
To fix the issue, I suggest we clear the "seekHintFilter" set before we further
execute any logic defined in the fiterKeyValue method. [~tedyu], what do you
think of this approach?
> 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-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.3.4#6332)
