[
https://issues.apache.org/jira/browse/HBASE-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191320#comment-13191320
]
Mikhail Bautin commented on HBASE-5230:
---------------------------------------
@Ted: the unit test failure at
https://builds.apache.org/job/PreCommit-HBASE-Build/824//testReport/org.apache.hadoop.hbase.regionserver/TestAtomicOperation/testRowMutationMultiThreads/
seems unrelated. Is this patch OK to be committed? (We can wait for another
run of unit tests if necessary, I've just re-uploaded the patch.)
> Unit test to ensure compactions don't cache data on write
> ---------------------------------------------------------
>
> Key: HBASE-5230
> URL: https://issues.apache.org/jira/browse/HBASE-5230
> Project: HBase
> Issue Type: Test
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Priority: Minor
> Attachments: D1353.1.patch, D1353.2.patch, D1353.3.patch,
> Don-t-cache-data-blocks-on-compaction-2012-01-21_00_53_54.patch,
> Don-t-cache-data-blocks-on-compaction-2012-01-23_10_23_45.patch
>
>
> Create a unit test for HBASE-3976 (making sure we don't cache data blocks on
> write during compactions even if cache-on-write is enabled generally
> enabled). This is because we have very different implementations of
> HBASE-3976 without HBASE-4422 CacheConfig (on top of 89-fb, created by Liyin)
> and with CacheConfig (presumably it's there but not sure if it even works,
> since the patch in HBASE-3976 may not have been committed). We need to create
> a unit test to verify that we don't cache data blocks on write during
> compactions, and resolve HBASE-3976 so that this new unit test does not fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
