[ 
https://issues.apache.org/jira/browse/CASSANDRA-18529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750910#comment-17750910
 ] 

Stefan Miklosovic commented on CASSANDRA-18529:
-----------------------------------------------

what would be interesting to see is that it would also work how it was. So 
people can opt-in into new simplified command or they can just use how it was. 
We could somehow "alias" it, not sure how complex that would be.

The format of the output of some tooling is considered to be something we 
strive to no break and it should be backward compatible. The command line 
arguments layout can be also considered to be something people are very 
sensitive to when it changes. We might go that extra mile to ensure we do not 
break things unnecessarily. 

> Remove legacy command line options from cassandra-stress
> --------------------------------------------------------
>
>                 Key: CASSANDRA-18529
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18529
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tool/stress
>            Reporter: Brad Schoening
>            Assignee: Timothy Tu
>            Priority: Low
>             Fix For: 5.x
>
>         Attachments: signature.asc
>
>
> The cassandra-stress *mode* option allows specifying options for native 
> protocol and cql3, but these don't seem useful as there would seem to be no 
> other valid options now that cql3 is the standard and thrift no longer 
> supported. 
>     -mode native cql3 user=cassandra password=xxxxxx
> can be simplified to:
>     -mode user=cassandra password=xxxxxx
> Also, the readme.txt in tools/stress states "cassandra-stress supports 
> benchmarking any Cassandra cluster of version 2.0+" but maybe should be 
> updated to a supported Cassandra version, i.e., 3.11.x.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to