hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asaf Mesika (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6954) Column-counting filters can accept multiple versions of a column
Date Sun, 14 Jul 2013 07:38:50 GMT

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

Asaf Mesika commented on HBASE-6954:
------------------------------------

I agree. If you set versions=3 you would expect to have no more than 3 in your filter. Maybe
the column counting can be done a little bit differently to address the problem in the code
comment.
                
> 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

Mime
View raw message