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

Eric Evans commented on CASSANDRA-3119:
---------------------------------------

bq. ... the old syntax was broken – we never actually supported a list there, 
which is what it implies.

I agree completely, but a user whose script has broken is still going to be 
irritated.

These things are like paper cuts, they aren't a huge deal when looked at in 
isolation, but they add up to a negative experience pretty quickly.

> Cli syntax for creating keyspace is inconsistent in 1.0
> -------------------------------------------------------
>
>                 Key: CASSANDRA-3119
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3119
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: Sylvain Lebresne
>            Assignee: T Jake Luciani
>            Priority: Minor
>              Labels: cli
>             Fix For: 1.0
>
>
> In 0.8, to create a keyspace you could do:
> {noformat}
> create keyspace test with placement_strategy = 
> 'org.apache.cassandra.locator.SimpleStrategy' and strategy_options = 
> [{replication_factor:3}]
> {noformat}
> In current trunk, if you try that, you get back "null". Turns out this is 
> because the syntax for strategy_options has changed and you should not use 
> the brackets, i.e:
> {noformat}
> strategy_options = {replication_factor:3}
> {noformat}
> (and note that reversely, this syntax doesn't work in 0.8).
> I'm not sure what motivated that change but this is very user unfriendly. The 
> help does correctly mention the new syntax, but it is the kind of changes 
> that takes you 5 minutes to notice. It will also break people scripts for no 
> good reason that I can see.
> We should either:
> # revert to the old syntax
> # support both the new and old syntax
> # at least print a meaningful error message when the old syntax is used
> Imho, the last solution is by far the worst solution.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to