cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6969) Use Unsafe Mutations Where Possible in Unit Tests
Date Tue, 01 Apr 2014 20:13:15 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956970#comment-13956970
] 

Tyler Hobbs commented on CASSANDRA-6969:
----------------------------------------

I'm not sure why we use batch CL for the tests.  If you're correct and the purpose is to exercise
batch CL, we should just make sure it's properly tested elsewhere.  I'd argue that having
slow unit tests is hurting our stability more than not using batch CL for unit tests would.

> Use Unsafe Mutations Where Possible in Unit Tests
> -------------------------------------------------
>
>                 Key: CASSANDRA-6969
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6969
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Tyler Hobbs
>            Assignee: Lyuben Todorov
>            Priority: Minor
>
> Since the test config uses the "batch" mode for the commitlog, safe writes are quite
slow.  In tests that don't rely on safe writes, we should use unsafe writes.  This mostly
consists of converting {{RowMutation.apply()}} calls into {{RowMutation.applyUnsafe()}} calls.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message