You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (JIRA)" <ji...@apache.org> on 2012/09/12 01:14:07 UTC

[jira] [Updated] (CASSANDRA-4649) Cassandra 1.2 should not accept CQL version "3.0.0-beta1"

     [ https://issues.apache.org/jira/browse/CASSANDRA-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

paul cannon updated CASSANDRA-4649:
-----------------------------------

    Description: 
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.
         Labels: cql3  (was: )
    
> Cassandra 1.2 should not accept CQL version "3.0.0-beta1"
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-4649
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4649
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2.0
>            Reporter: paul cannon
>            Priority: Minor
>              Labels: cql3
>
> 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: http://www.atlassian.com/software/jira