[ https://issues.apache.org/jira/browse/CASSANDRA-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982624#comment-14982624 ]
Paulo Motta commented on CASSANDRA-10513: ----------------------------------------- bq. there seems to be new failures due to this, typically {{complex_schema_test}} my bad for not spotting this, with the avalanche of unrelated dtest failures I only checked the explicit {{cqlsh*.py}} tests, forgot that there were also cqlsh tests on {{json_tests.py}} It seems with the [removal|https://github.com/datastax/python-driver/commit/827f6a2c7974f0c158933b54b281a9ff8de63e97] of blist as dependency from the driver there was a change in {{sortedset}} representation from [this|https://github.com/DanielStutzbach/blist/blob/0ed541a5f5fce18b3a8535d32ec64eef78485044/blist/_sortedlist.py#L621] to [this|https://github.com/datastax/python-driver/blob/827f6a2c7974f0c158933b54b281a9ff8de63e97/cassandra/util.py#L518]. Can we restore the original representation in the driver (as other clients might be also relying on that), or should we fix on cqlsh? > Update cqlsh for new driver execution API > ----------------------------------------- > > Key: CASSANDRA-10513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10513 > Project: Cassandra > Issue Type: New Feature > Components: Tools > Reporter: Adam Holmberg > Assignee: Adam Holmberg > Priority: Minor > Labels: cqlsh > Fix For: 2.2.4, 3.0.0 > > 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|https://datastax-oss.atlassian.net/browse/PYTHON-368] > [Trace data is always attached to the > ResultSet|https://datastax-oss.atlassian.net/browse/PYTHON-318] (instead of > being attached to a statement) -- This message was sent by Atlassian JIRA (v6.3.4#6332)