You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/02/10 12:56:40 UTC

[jira] [Commented] (CASSANDRA-8298) cassandra-stress legacy

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

Benedict commented on CASSANDRA-8298:
-------------------------------------

I'm kind of tempted to drop support for legacy legacy. I know it was there for 2.0 users, but we're already heading to have a legacy mode within 2.1 (i.e. non-user mode)

>  cassandra-stress legacy
> ------------------------
>
>                 Key: CASSANDRA-8298
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8298
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: Centos 6.5 Cassandra 2.1.1
>            Reporter: Edgardo Vega
>            Assignee: T Jake Luciani
>
> Running cassandra-stress legacy failed immediately with a error.
> 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)



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