[ https://issues.apache.org/jira/browse/CASSANDRA-12695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636349#comment-15636349 ]
T Jake Luciani commented on CASSANDRA-12695: -------------------------------------------- Why not just make the check ... {code} || (settings.rate.threadCount != -1 && settings.command.truncate == SettingsCommand.TruncateWhen.ALWAYS) {code} > Truncate ALWAYS not applied > --------------------------- > > Key: CASSANDRA-12695 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12695 > Project: Cassandra > Issue Type: Bug > Reporter: Alwyn Davis > Priority: Trivial > Labels: stress > Fix For: 3.x > > Attachments: 12695-trunk.patch > > > If truncate is set to ALWAYS and rate sets a specific thread count, the > stress table is not actually truncated. E.g. > {code} > truncate=always -rate threads=4 > {code} > This can cause an unexpected number of rows to be left in the table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)