[
https://issues.apache.org/jira/browse/CASSANDRA-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-4844.
-----------------------------------------
Resolution: Won't Fix
Yes, the syntax has changed in a breaking way. In fact, that's not even the
biggest breaking change in that we've also removed the consistency level from
the language (to move it to the protocol level). This is unfortunate *but*
we've bee clear that CQL3 was beta in 1.1 (I admit the datastax doc isn't that
clear and I'll ask them to do something about it, but the official CQL3 doc for
1.1 is: http://cassandra.apache.org/doc/cql3/CQL.html). I note that this is
indicated in the NEWS file.
> CQL3 Create keyspace statement not compatible with older versions.
> ------------------------------------------------------------------
>
> Key: CASSANDRA-4844
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4844
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Edward Capriolo
>
> Following the advice here.
> http://www.datastax.com/docs/1.1/dml/using_cql
> {noformat}
> [edward@tablitha apache-cassandra-1.2.0-beta1]$ bin/cqlsh -3
> Connected to Test Cluster at localhost:9160.
> [cqlsh 2.2.0 | Cassandra 1.2.0-beta1 | CQL spec 3.0.0 | Thrift protocol
> 19.34.0]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE demodb WITH strategy_class =
> 'org.apache.cassandra.locator.SimpleStrategy' AND
> strategy_options:replication_factor='1' ;
> Bad Request: line 1:129 mismatched input ':' expecting '='
> Perhaps you meant to use CQL 2? Try using the -2 option when starting cqlsh.
> {noformat}
> http://www.datastax.com/docs/1.1/references/cql/CREATE_KEYSPACE
> {noformat}
> cqlsh> CREATE KEYSPACE Excelsior WITH strategy_class = 'SimpleStrategy'
> ... AND strategy_options:replication_factor = 1;
> Bad Request: line 2:22 mismatched input ':' expecting '='
> {noformat}
> It seems that in Cassandra 1.2 I am no longer able to create a keyspace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
