[ https://issues.apache.org/jira/browse/CASSANDRA-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924157#comment-13924157 ]
Tyler Hobbs commented on CASSANDRA-6307: ---------------------------------------- Overall, the changes look really good. There are a few methods leftover that have an identical version in the driver: * cql3handling.escape_name => cassandra.metadata.escape_name * cql3handling.maybe_escape_name => cassandra.metadata.maybe_escape_name * cql3handling.valid_cql3_word_re => cassandra.metadata.valid_cql3_word_re * cqlsh.cql_protect_name(s) => cassandra.metadata.protect_name(s) * cqlsh.cql_protect_value => cassandra.metadata.protect_value cqlsh is still duplicating some of the driver's built-in tracing (which is also a little more fault-tolerant). I'm okay with pushing that improvement to another ticket. I would like to have a debug option that enables the driver's logging, but that can also be pushed to another ticket. > 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)