Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 14 Apr 2011 16:41:06 +0000 (UTC)
From: "Eric Evans (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <119897346.58087.1302799266213.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <32460245.7991288877263130.JavaMail.jira@thor>
Subject: [jira] [Resolved] (CASSANDRA-1703) CQL 1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Evans resolved CASSANDRA-1703.
-----------------------------------

    Resolution: Fixed
      Assignee: Eric Evans

The release goals for CQL 1.0 are complete; Closing this issue.

> CQL 1.0
> -------
>
>                 Key: CASSANDRA-1703
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1703
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>    Affects Versions: 0.8
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>            Priority: Minor
>              Labels: cql
>             Fix For: 0.8
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> CQL (Cassandra Query Language) is a proposed language for data management in Cassandra.
> This issue is meant to encapsulate the goals for CQL in the next stable release (0.8), roughly:
> * Completed 1.0 language specification.
> * Implementation of the language using the Avro interface for transport and serialization.
> * Low-level drivers for Java and Python (possibly others).
> * The deprecation (or removal, TBD) of (Avro) RPC methods.
> Separate tickets with the appropriate relationships to this one will be created for the individual tasks.
> *Edit (2011-01-21): Changed short description from "CQL 1.0" to "CQL 0.99".*
> *Edit (2011-04-14): Changed it back.  Whatever.*
> CQL 1.0 needn't be entirely complete, but it should be stable. Backward incompatible changes mean a transition to 2.0 (and I hope there is never a 2.0).  However, I don't think it will have baked long enough to be called "1.0" in the next release (0.7+1), so let's call that 0.99 (to signal the possibility of backward incompatible changes), and target 0.7+2 for CQL 1.0.

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