[ 
https://issues.apache.org/jira/browse/CASSANDRA-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefania updated CASSANDRA-13773:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 4.0
                   3.11.1
           Status: Resolved  (was: Patch Available)

dtests looked good as well.

I don't think anyone would expect cassandra-stress to write data if n=0, so 
I've committed it to 3.0 as {{6a1b1f26b7174e8c9bf86a96514ab626ce2a4117}} and 
merged into 3.11 and trunk.

> 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, 3.11.1, 4.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to