cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4649) Cassandra 1.2 should not accept CQL version "3.0.0-beta1"
Date Wed, 12 Sep 2012 13:14:09 GMT


Sylvain Lebresne updated CASSANDRA-4649:

    Attachment: 4649.txt

Patch attached that
* changes the version to 3.0.0 (we don't have anything in store that would need to break syntax
further and we're about to roll 1.2.0 beta1 soon (hopefully) so I think it's indeed time to
drop the beta).
* Makes 1.2 refuse 3.0.0-beta1 version (with an hopefully useful error message).

I note however that 1.1 was happily accepting 3.0.0 as a version, and I don't think we have
advertised much that people should use 3.0.0-beta1 in 1.1, so most people will be surprised
that their CREATE KEYSPACE query is invalid all of a sudden anyway (including user of cqlsh).
We do have a NEWS entry to explain that however so not sure there is more we can/need to do.

> Cassandra 1.2 should not accept CQL version "3.0.0-beta1"
> ---------------------------------------------------------
>                 Key: CASSANDRA-4649
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2.0
>            Reporter: paul cannon
>            Priority: Minor
>              Labels: cql3
>         Attachments: 4649.txt
> During Cassandra 1.1's whole lifecycle, the CREATE KEYSPACE syntax was pretty dramatically
and incompatibly different from what is there now for 1.2. That's ok, since we explicitly
said there could be breaking changes in the syntax before 3.0.0 final, but at least we should
make it clear that 3.0.0 is not compatible with the 3.0.0-beta1 syntax we had out for quite
a while.
> If we don't want to reject connections asking for 3.0.0-beta1, we should bump the version
number to 3.0.1 or something.

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:

View raw message