cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3990) cqlsh support for CQL 3
Date Fri, 30 Mar 2012 17:30:27 GMT


Sylvain Lebresne commented on CASSANDRA-3990:

Some part of me tell me that this may prove limiting. I've actually bothered implementing
the semantic versioning server side, so that when for instance when we have cql 3.1.0, if
the client asked for 3.1.0 but the server is an old one that only support 3.0.0, an error
is returned. So in other words, we will later need to be able to distinguish between 3.0.0
and 3.1.0. Feels like adding a specific flag each time will prove limiting or tedious to upgrade.
I'm not sure if that would really matter for cqlsh but just figured I'd mention it.

Maybe we could still have the option of setting whatever version we want, but then have --cql2
and --cql3 shortcuts that would refer to the more recent known version for instance.

> cqlsh support for CQL 3
> -----------------------
>                 Key: CASSANDRA-3990
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>            Reporter: Sylvain Lebresne
>            Assignee: Eric Evans
>            Priority: Minor
>             Fix For: 1.1.0
>         Attachments: v1-0001-CASSANDRA-3990-cqlsh-support-for-CQL-3.txt, v2-0001-CASSANDRA-3990-cqlsh-support-for-CQL-3.txt
> Cqlsh needs to add support for CQL3. At a minimum, one needs to be able to choose the
cql version at launch time.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message