cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12150) cqlsh does not automatically downgrade CQL version
Date Tue, 12 Jul 2016 16:09:20 GMT


Tyler Hobbs commented on CASSANDRA-12150:

bq. I would need a code review of this commit, Tyler Hobbs would you be able to review it?

+1 on that commit.

bq. We should probably mention somewhere that, even though cqlsh now connects to older server
versions, there may be problems and it may not work in all cases since we currently do not
test cqlsh against older server versions

Yes, I think we should at least put something in {{NEWS.txt}} for now.  Perhaps if this causes
frequent problems, we can have cqlsh print a warning when the C* version it connects to is
different than the C* version it shipped with.

> cqlsh does not automatically downgrade CQL version
> --------------------------------------------------
>                 Key: CASSANDRA-12150
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Yusuke Takata
>            Priority: Minor
>              Labels: cqlsh
>         Attachments: patch.txt
> Cassandra drivers such as the Python driver can automatically connect a supported version,

> but I found that cqlsh does not automatically downgrade CQL version as the following.
> {code}
> $ cqlsh
> Connection error: ('Unable to connect to any servers', {'': ProtocolError("cql_version
'3.4.2' is not supported by remote (w/ native protocol). Supported versions: [u'3.4.0']",)})
> {code}
> I think that the function is useful for cqlsh too. 
> Could someone review the attached patch?

This message was sent by Atlassian JIRA

View raw message