[
https://issues.apache.org/jira/browse/HBASE-20565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480064#comment-16480064
]
Zheng Hu commented on HBASE-20565:
----------------------------------
FilterList concated by ColumnRangeFilter & ColumnPaginationFilter (offset,
limit) is in conflict with the Max Step Rule. but FilterList concated by
ColumnRangeFilter & ColumnPaginationFilter(limit) or
ColumnPaginationFilter(byte[], limit) has no problem. Does it make sense
that setting an offset & limit for ColumnPaginationFilter ? This scene can be
completely replaced by ColumnPaginationFilter(byte[], limit) ?
[~anoop.hbase], how do you think ?
> ColumnRangeFilter combined with ColumnPaginationFilter can produce incorrect
> result since 1.4
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-20565
> URL: https://issues.apache.org/jira/browse/HBASE-20565
> Project: HBase
> Issue Type: Bug
> Components: Filters
> Affects Versions: 1.4.4
> Reporter: Jerry He
> Assignee: Zheng Hu
> Priority: Major
> Attachments: debug.diff, debug.log, test-branch-1.4.patch
>
>
> When ColumnPaginationFilter is combined with ColumnRangeFilter, we may see
> incorrect result.
> Here is a simple example.
> One row with 10 columns c0, c1, c2, .., c9. I have a ColumnRangeFilter for
> range c2 to c9. Then I have a ColumnPaginationFilter with limit 5 and offset
> 0. FileterList is FilterList(Operator.MUST_PASS_ALL, ColumnRangeFilter,
> ColumnPaginationFilter).
> We expect 5 columns being returned. But in HBase 1.4 and after, 4 columns
> are returned.
> In 1.2.x, the correct 5 columns are returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
