cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12150) cqlsh does not automatically downgrade CQL version
Date Fri, 08 Jul 2016 16:45:11 GMT

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

Aleksey Yeschenko commented on CASSANDRA-12150:
-----------------------------------------------

I'm not sure how that check, or the concept of cql version, is really useful at all, to be
honest. Definitely for cqlsh.

> cqlsh does not automatically downgrade CQL version
> --------------------------------------------------
>
>                 Key: CASSANDRA-12150
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12150
>             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', {'127.0.0.1': 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
(v6.3.4#6332)

Mime
View raw message