cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10513) Update cqlsh for new driver execution API
Date Wed, 28 Oct 2015 00:28:28 GMT


Paulo Motta commented on CASSANDRA-10513:

It seems there are some new test failures with {{cqlsh_tests.cqlsh_copy_tests}} on [3.0|]
and [2.2|]
(they do not appear in the original [2.2|]
and [3.0|]

On [2.1|]
and [2.2|]
there seems to be a new failure on {{cqlsh_tests.cqlsh_tests.TestCqlsh.test_describe}} probably
due to the driver upgrade from 2.7.2 to 3.0.0.

On 2.1 there is also a new failure on [cqlsh_tests.cqlsh_tests.TestCqlsh.test_refresh_schema_on_timeout_error|].

Would you mind having a look on these? I wonder if we should bother upgrading the cqlsh internal
driver on 2.1, since it will be EOL soon. I think we should probably stick to 2.2 and 3.0,
what do you think [~aholmber] ?

> Update cqlsh for new driver execution API
> -----------------------------------------
>                 Key: CASSANDRA-10513
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Adam Holmberg
>            Assignee: Paulo Motta
>            Priority: Minor
>              Labels: cqlsh
>             Fix For: 2.2.x, 3.0.x
>         Attachments: 10513-2.1.txt, 10513-2.2.txt, 10513.txt
> The 3.0 Python driver will have a few tweaks to the execution API. We'll need to update
cqlsh in a couple of minor ways.
> [Results are always returned as an iterable ResultSet|]
> [Trace data is always attached to the ResultSet|]
(instead of being attached to a statement)

This message was sent by Atlassian JIRA

View raw message