Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 809A29A5B for ; Thu, 2 Feb 2012 17:11:34 +0000 (UTC) Received: (qmail 38960 invoked by uid 500); 2 Feb 2012 17:11:32 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 38883 invoked by uid 500); 2 Feb 2012 17:11:31 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 38871 invoked by uid 99); 2 Feb 2012 17:11:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 17:11:30 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tamil.3758@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qw0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 17:11:25 +0000 Received: by qan41 with SMTP id 41so1732515qan.10 for ; Thu, 02 Feb 2012 09:11:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Pi0kNcIx/dGy0GUweOnjg6kgX5A/rN5aRagemtV2pa0=; b=pn60buanKiM3D12HINOXfbXUNghRFDt2JBfjZVVxPRA59ZnAcYwYKt0u+CysH33d64 weMPolRPsfMTxuK3H5D3okbzWOwDTF0LpGnyLfqkkOu+ONnyCyztuIPrN8Ftp4vNBI7u 9XZZYa1AQJVdM2yxDmCIpuMa2ekvFN2p2SrIA= MIME-Version: 1.0 Received: by 10.224.117.15 with SMTP id o15mr5065227qaq.97.1328202664842; Thu, 02 Feb 2012 09:11:04 -0800 (PST) Received: by 10.229.77.85 with HTTP; Thu, 2 Feb 2012 09:11:04 -0800 (PST) In-Reply-To: References: Date: Thu, 2 Feb 2012 22:41:04 +0530 Message-ID: Subject: Re: Schedule for CQL 1.1 From: "Tamil selvan R.S" To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf3020759207156204b7fe48c2 --20cf3020759207156204b7fe48c2 Content-Type: text/plain; charset=ISO-8859-1 Thank you Eric :) Regards, Tamil Selvan On Wed, Feb 1, 2012 at 10:08 PM, Eric Evans wrote: > On Wed, Feb 1, 2012 at 5:50 AM, Tamil selvan R.S > wrote: > > Where to follow the progress of Cassandra CQL development progress and > > release schedule? > > We don't have a formal roadmap for this I'm afraid. Your best bet is > to search the issue tracker for CQL tickets, and follow the list. > > At the moment there are 2 branches of development, CQLv2 and CQLv3. > > CQLv3 (which will debut in the upcoming 1.1 release) is a significant > departure in a number of important ways, including support for > wide-rows which use the compound column approach to create indexed, > tabular structures from rows. See > https://issues.apache.org/jira/browse/CASSANDRA-2474 (if you dare) and > https://issues.apache.org/jira/browse/CASSANDRA-3761 for more. > > CQLv2 will remain the default for now, and CQLv3 will be available as > a run-time option. When consensus is that CQLv3 is feature-complete > and ready for production use, it will become the new default, and > CQLv2 will be available as a run-time option for legacy clients (this > isn't expected to happen before 1.2). > > Hope this helps. > > -- > Eric Evans > Acunu | http://www.acunu.com | @acunu > --20cf3020759207156204b7fe48c2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thank you Eric :)

Regards,
Tamil Selvan
On Wed, Feb 1, 2012 at 10:08 PM, Eric Evans <eevans@acunu.com= > wrote:
On Wed, Feb 1, 2012 at 5:5= 0 AM, Tamil selvan R.S <tamil.37= 58@gmail.com> wrote:
> =A0Where to follow the progress of Cassandra CQL development progress = and
> release schedule?

We don't have a formal roadmap for this I'm afraid. =A0Your b= est bet is
to search the issue tracker for CQL tickets, and follow the list.

At the moment there are 2 branches of development, CQLv2 and CQLv3.

CQLv3 (which will debut in the upcoming 1.1 release) is a significant
departure in a number of important ways, including support for
wide-rows which use the compound column approach to create indexed,
tabular structures from rows. =A0See
https://issues.apache.org/jira/browse/CASSANDRA-2474 (if you da= re) and
https://issues.apache.org/jira/browse/CASSANDRA-3761 for more.<= br>
CQLv2 will remain the default for now, and CQLv3 will be available as
a run-time option. =A0When consensus is that CQLv3 is feature-complete
and ready for production use, it will become the new default, and
CQLv2 will be available as a run-time option for legacy clients (this
isn't expected to happen before 1.2).

Hope this helps.

--
Eric Evans
Acunu |=A0http://www.acu= nu.com=A0| @acunu

--20cf3020759207156204b7fe48c2--