Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1321977224.449751266886170875.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Feb 2010 00:49:30 +0000 (UTC)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2249) The PerformanceEvaluation read tests
 don't take the MemStore into account.
In-Reply-To: <1049968996.449731266886051000.JavaMail.jira@brutus.apache.org>
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:comment-tabpanel&focusedCommentId=12837014#action_12837014 ] 

Jean-Daniel Cryans commented on HBASE-2249:
-------------------------------------------

Good idea Dan!

> 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.4
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.