Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <16678566.34131276712903311.JavaMail.jira@thor>
Date: Wed, 16 Jun 2010 14:28:23 -0400 (EDT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Resolved: (HBASE-2738) Fix TestTimeRangeMapRed verification
 now that we store multiple versions with same TS
In-Reply-To: <25865696.33311276711348917.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon resolved HBASE-2738.
--------------------------------

    Hadoop Flags: [Reviewed]
      Resolution: Fixed

> Fix TestTimeRangeMapRed verification now that we store multiple versions with same TS
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-2738
>                 URL: https://issues.apache.org/jira/browse/HBASE-2738
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.21.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.21.0
>
>         Attachments: hbase-2738.txt
>
>
> We recently introduced "memstore timestamps" which are internal, and allow a cell to exist twice with the same timestamp, from different puts. TestTimeRangeMapred now fails since it sees both the old and new version of the cells during verification. Setting the max versions of the verification scanner to 1 fixes it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.