[jira] Updated: (HBASE-2249) The PerformanceEvaluation read tests don't take the MemStore into account.

["stack (JIRA)" <ji...@apache.org>]

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

stack updated HBASE-2249:
-------------------------

    Attachment: HBASE-2249_v2.patch

This patch was idling on my machine.  It was sent by author a few weeks ago but I forgot about it.  

Here is commit message:

{code}
calling HBaseAdmin.flushTable instead of the the HTable.flushCommits
including the call to HTable.flushCommits within the timer (as per email from Bob Jacoby)
fix bug with flushCommits argument parsing
renamed flushCommits argument to flushTable
{code}

Please review J-D.

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