Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Later
-
0.20.3
-
None
Description
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...
Attachments
Attachments
Issue Links
- is related to
-
HBASE-2248 Provide new non-copy mechanism to assure atomic reads in get and scan
- Closed