Cassandra-stress frontend always creates standard1 and counter1 tables for all workloads (user is exception). At the time of implementing this, I was sure that original c-s does the same - apparently I was wrong.
In general, the tables we should create for each workload:
write/read - standard1 table
counter/counter_read - counter1 table
mixed - both standard1 and counter1 tables. Better idea might be to create the tables that will be used by the commands provided by the user - e.g. when user provides ratio(write=1,read=2), we should not create counter1 table since it won't be used
user - a table defined in yaml file with table and table_definition parameters
Ref: https://github.com/scylladb/scylladb/issues/19107#issuecomment-2155038858
Cassandra-stress frontend always creates
standard1andcounter1tables for all workloads (useris exception). At the time of implementing this, I was sure that original c-s does the same - apparently I was wrong.In general, the tables we should create for each workload:
write/read-standard1tablecounter/counter_read-counter1tablemixed- bothstandard1andcounter1tables. Better idea might be to create the tables that will be used by the commands provided by the user - e.g. when user providesratio(write=1,read=2), we should not createcounter1table since it won't be useduser- a table defined in yaml file withtableandtable_definitionparameters