[
https://issues.apache.org/jira/browse/CASSANDRA-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-3780.
-----------------------------------------
Resolution: Not A Problem
While committing CASSANDRA-3761, I've switched the default back to CQL 2.0, as
I don't want to make life harder for people that want to test 1.1 given it'll
enter the freeze basically now.
I've created
http://code.google.com/a/apache-extras.org/p/cassandra-dbapi2/issues/detail?id=14&thanks=14&ts=1327495681,
with an initial patch at
https://github.com/pcmanus/python-cql/tree/version_support to add support for
setting the version in the CQL driver, so we can continue working on CQL 3.0.
I've also update the tests at https://github.com/riptano/cassandra-dtest
accordingly (it's all in the master branch now because I somehow screwed up and
merged the cql3_tests branch there).
> cassandra defaults to CQLv3
> ---------------------------
>
> Key: CASSANDRA-3780
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3780
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
> Affects Versions: 1.1
> Reporter: Eric Evans
> Labels: cql
> Fix For: 1.1
>
>
> Cassandra defaults to CQLv3, a temporary measure to facilitate testing. At
> some point this needs to be defaulted back to CQLv2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
