[
https://issues.apache.org/jira/browse/CASSANDRA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926025#comment-13926025
]
Mikhail Stepura commented on CASSANDRA-6307:
--------------------------------------------
bq. cqlsh is still duplicating some of the driver's built-in tracing (which is
also a little more fault-tolerant).
[~thobbs] is it possible to get a trace for any session which was traced
before? I believe the driver only populates {{trace}} for statements executed
with {{trace=True}}. But CQLSH has to support {{SHOW SESSION <uuid>}} command,
for any particular session, and I see no way to retrieve that info from the
driver
bq. There are a few methods leftover that have an identical version in the
driver
Will take a look
bq. we can (and should) finally add support for client SSL certs.
Will take a look
> Switch cqlsh from cassandra-dbapi2 to python-driver
> ---------------------------------------------------
>
> Key: CASSANDRA-6307
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6307
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksey Yeschenko
> Assignee: Mikhail Stepura
> Priority: Minor
> Fix For: 2.1 beta2
>
>
> python-driver is hitting 1.0 soon. cassandra-dbapi2 development has stalled.
> It's time to switch cqlsh to native protocol and cassandra-dbapi2, especially
> now that
> 1. Some CQL3 things are not supported by Thrift transport
> 2. cqlsh no longer has to support CQL2 (dropped in 2.0)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
