You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Olson (JIRA)" <ji...@apache.org> on 2012/10/04 23:53:47 UTC

[jira] [Updated] (HBASE-6954) Column-counting filters can accept multiple versions of a column

     [ https://issues.apache.org/jira/browse/HBASE-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Olson updated HBASE-6954:
--------------------------------

    Attachment: ColumnPaginationFilterTest.java
    
> Column-counting filters can accept multiple versions of a column
> ----------------------------------------------------------------
>
>                 Key: HBASE-6954
>                 URL: https://issues.apache.org/jira/browse/HBASE-6954
>             Project: HBase
>          Issue Type: Bug
>          Components: Filters
>            Reporter: Andrew Olson
>         Attachments: ColumnPaginationFilterTest.java
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira