[
https://issues.apache.org/jira/browse/HBASE-9155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766724#comment-13766724
]
Sergey Shelukhin commented on HBASE-9155:
-----------------------------------------
I meant that if update follows write close they will usually end up just being
in memstore... scanner merging, compaction of values for the same key from
multiple files etc. will never happen. In fact most reads will be served from
memstore probably (I am adding random reader threads). When I was manually
testing compactions the correctness of reads when compaction is dropping stuff
from old files/merging deletes/etc. was important. But nm we can take of it
later if needed.
> Enhance LoadTestTool to support updates
> ---------------------------------------
>
> Key: HBASE-9155
> URL: https://issues.apache.org/jira/browse/HBASE-9155
> Project: HBase
> Issue Type: Test
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.98.0, 0.95.2
>
> Attachments: trunk-9155.patch
>
>
> We can enhance LoadTestTool to support updates like
> increment/append/checkAndPut/checkAndDelete to make sure these operations
> work as expected during integration testing.
> If chaosmonkey is enabled, increment/append could be invoked multiple times.
> During verification, we need to keep this in mind before they are guaranteed
> to be called only once in the sever side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
