cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9161) Add random interleaving for flush/compaction when running CQL unit tests
Date Fri, 24 Apr 2015 09:03:39 GMT


Sylvain Lebresne commented on CASSANDRA-9161:

Initially, I was just thinking of what I call for lack of a better term "CQL tests", i.e.
those unit tests which really are testing a particular CQL syntax/feature, not exercising
a bug linked to flush/compaction or some more low-level feature (that's most of the tests
in the cql3 package in practice). For those "CQL tests", I think it makes sense to just use
random flush/compaction and drop any manual one if there is some (but pretty sure almost all
of the tests I'm thinking of don't do it in the first place).

There will be tests that want to flush/compact at specific places to do something meaningful
and we should probably preserve them. I was thinking of either having a separate class for
tests for which randomizing flush/compaction is meaningful or add a per-test annotation. I
suspect a separate class is a good enough granularity however.

> Add random interleaving for flush/compaction when running CQL unit tests
> ------------------------------------------------------------------------
>                 Key: CASSANDRA-9161
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sylvain Lebresne
>              Labels: retrospective_generated
> Most CQL tests don't bother flushing, which means that they overwhelmingly test the memtable
path and not the sstables one. A simple way to improve on that would be to make {{CQLTester}}
issue flushes and compactions randomly between statements.

This message was sent by Atlassian JIRA

View raw message