Mailing-List: contact hbase-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <5023732.27691271175712044.JavaMail.jira@thor>
Date: Tue, 13 Apr 2010 12:21:52 -0400 (EDT)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: hbase-issues@hadoop.apache.org
Subject: [jira] Updated: (HBASE-2249) The PerformanceEvaluation read tests
 don't take the MemStore into account.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell updated HBASE-2249:
----------------------------------

    Status: Open  (was: Patch Available)

Cancelling patch. Stale, please rebase.

> The PerformanceEvaluation read tests don't take the MemStore into account.
> --------------------------------------------------------------------------
>
>                 Key: HBASE-2249
>                 URL: https://issues.apache.org/jira/browse/HBASE-2249
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.20.3
>            Reporter: Dan Washusen
>             Fix For: 0.20.5, 0.21.0
>
>         Attachments: 2249-TRUNK.patch, HBASE-2249.patch, HBASE-2249_v2.patch
>
>
> The write tests in the PerformanceEvaluation flush the MemStore after they complete, as a result the read tests don't take the MemStore into account (because it's always empty).  An optional flag could be provided when the performance evaluation starts that dictates if the table should be flushed after a test completes.  This optional flag would allow changes to the MemStore to be performance tested...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira