You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/02/18 05:00:20 UTC

[jira] [Commented] (CASSANDRA-5918) Remove CQL2 entirely from Cassandra 3.0

    [ https://issues.apache.org/jira/browse/CASSANDRA-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903759#comment-13903759 ] 

Aleksey Yeschenko commented on CASSANDRA-5918:
----------------------------------------------

Pushed the commit to https://github.com/iamaleksey/cassandra/commits/5918.

Not sure what to do with thirft definitions (besides obviously bumping the major). Throw IRE for all the CQL2 methods (as in the commit), or get rid of them altogether, erasing the last and only traces of CQL2 existence (other than NEWS and CHANGES).

> Remove CQL2 entirely from Cassandra 3.0
> ---------------------------------------
>
>                 Key: CASSANDRA-5918
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5918
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>              Labels: cql
>             Fix For: 3.0
>
>
> CQL2 is officially no longer worked on since 1.2. cqlsh no longer supports CQL2 as of Cassandra 2.0.
> It's probably the time to deprecate CQL2 in 2.0 and to remove it entirely in 2.2 - there is nothing in CQL2 now that can't be done via CQL3 and two versions advance warning is plenty of time for those few still using CQL2 to switch to CQL3.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)