Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 5 Oct 2012 08:51:47 +1100 (NCT)
From: "Andrew Olson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <525163217.2503.1349387507321.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HBASE-6954) Column-counting filters can accept
 multiple versions of a column
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andrew Olson created HBASE-6954:
-----------------------------------

             Summary: 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


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