Benedict created CASSANDRA-8600:
-----------------------------------
Summary: Refactor stress options to reduce prominence of legacy
modes (counter_read, etc.)
Key: CASSANDRA-8600
URL: https://issues.apache.org/jira/browse/CASSANDRA-8600
Project: Cassandra
Issue Type: Improvement
Components: Tools
Reporter: Benedict
Priority: Minor
There;s an asymmetry to how we treat these, with all four legacy commands
(read, write, counter_read, counter_write) getting their own full-blown
command, whereas the "user" command is comparatively almost hidden. There are
also two option sets that apply only to the legacy commands ("schema" and
"cols") which isn't at all apparent.
We should clean this up, by e.g. renaming "user" to "profile" or something more
obvious, and dropping the four old commands and renaming "mixed" to "simple" -
this would give "simple" a similar spec style to "profile". We should then make
it clear that "cols" and "schema" only apply to the "simple" mode, and should
fail if they are supplied otherwise.
We can of course continue to accept all of the old ways of specifying commands
if we want, and just not print them out in the help.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
