[jira] [Commented] (CASSANDRA-11795) cassandra-stress legacy mode fails - time to remove it?

["T Jake Luciani (JIRA)" <ji...@apache.org>]

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

T Jake Luciani commented on CASSANDRA-11795:
--------------------------------------------

Yes I totally agree... 

> cassandra-stress legacy mode fails - time to remove it?
> -------------------------------------------------------
>
>                 Key: CASSANDRA-11795
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11795
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Michael Shuler
>            Assignee: T Jake Luciani
>            Priority: Minor
>              Labels: stress
>             Fix For: 3.x
>
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ cassandra-stress legacy -o INSERT
> Running in legacy support mode. Translating command to: 
> stress write n=1000000 -col n=fixed(5) size=fixed(34) data=repeat(1) -rate threads=50 -log interval=10 -mode thrift
> Invalid parameter data=repeat(1)
> Usage:      cassandra-stress <command> [options]
> Help usage: cassandra-stress help <command>
> ---Commands---
> read                 : Multiple concurrent reads - the cluster must first be populated by a write test
> write                : Multiple concurrent writes against the cluster
> <...>
> {noformat}
> I tried legacy mode as a one-off, since someone provided a 2.0 stress option command line to duplicate. Is it time to remove legacy, perhaps?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)