[ https://issues.apache.org/jira/browse/CASSANDRA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134651#comment-16134651 ]
Stefania commented on CASSANDRA-13773: -------------------------------------- The patch LGTM however, whilst it doesn't make sense to perform warmup when n=0, it still changes the behavior seen by the user. Therefore, I am not entirely sure this patch should go into 3.0, any thoughts [~tjake]? Regarding CI, I think what we care is that dtests using cassandra-stress still work, I don't think cassandra-stress impacts unit tests at all. > cassandra-stress writes even data when n=0 > ------------------------------------------ > > Key: CASSANDRA-13773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13773 > Project: Cassandra > Issue Type: Bug > Components: Stress > Reporter: Eduard Tudenhoefner > Assignee: Eduard Tudenhoefner > Priority: Minor > Fix For: 3.0.15 > > > This is very unintuitive as > {code} > cassandra-stress write n=0 -rate threads=1 > {code} > will do inserts even with *n=0*. I guess most people won't ever run with > *n=0* but this is a nice shortcut for creating some schema without using > *cqlsh* > This is happening because we're writing *50k* rows of warmup data as can be > seen below: > {code} > cqlsh> select count(*) from keyspace1.standard1 ; > count > ------- > 50000 > (1 rows) > {code} > We can avoid writing warmup data using > {code} > cassandra-stress write n=0 no-warmup -rate threads=1 > {code} > but I would still expect to have *0* rows written when specifying *n=0*. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org