[HBASE-6954] Column-counting filters can accept multiple versions of a column

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Component/s: Filters
• Assignee: Unassigned
• Reporter: Andrew Olson
• Created: 04/Oct/12 21:50
• Updated: 14/Jun/22 21:25
• Resolved: 14/Jun/22 21:25

Description

It looks like the max version limit for a table or scanner is not applied to disregard older versions, prior to counting columns within a ColumnPaginationFilter or ColumnCountGetFilter. As a result, a Scan or Get can ultimately retrieve fewer than the requested number of columns when there is a sufficient number of existing columns to satisfy the request, if multiple versions of a column have been added to a row.

A minimal test case demonstrating this behavior is attached.

The javadoc for Get mentions 'Only Filter.filterKeyValue(KeyValue) is called AFTER all tests for ttl, column match, deletes and max versions have been run.'; for these two filters this behavior does not appear to be true, as flattening of multiple versions appears to occur after the filter has been applied.

Issue Links

• is related to: HBASE-5104 Provide a reliable intra-row pagination mechanism
• is related to: HBASE-5257 Allow INCLUDE_AND_NEXT_COL in filters and use it in ColumnPaginationFilter