[
https://issues.apache.org/jira/browse/HBASE-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853750#action_12853750
]
stack commented on HBASE-2249:
------------------------------
.bq So I'm not sure exactly what was committed to branch WRT to the title of
this issue.
Doesn't {code}$ svn diff -r919868:919875 .{code} tell you?
.bq This literally means that if flushCommits is false then we don't flush the
client write buffer to HBase... and this is the default value!
This looks like a misunderstanding on author's part. Let me ask. This issue
is supposed to be about memstore flushing, not client flushing. Sorry for any
inconvenience caused by my hasty commit.
> 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
>
>
> 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.
