[
https://issues.apache.org/jira/browse/CASSANDRA-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752652#comment-15752652
]
Sandeep Tamhankar commented on CASSANDRA-10145:
-----------------------------------------------
Just confirmed that my branch (PYTHON-684) has been merged to master. We're
ready to merge that down to cassandra-test and move things forward. I believe
accepting this patch and merging the Python driver master to cassandra-test
branch need to happen simultaneously. If the Python driver branch is merged
down first, it will speak the "new" v5 against existing C* and dtests will fail.
[~thobbs] I think you have the power in both repos, so I defer to you.
> Change protocol to allow sending key space independent of query string
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-10145
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10145
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Vishy Kasar
> Assignee: Sandeep Tamhankar
> Fix For: 3.x
>
> Attachments: 10145-trunk.txt
>
>
> Currently keyspace is either embedded in the query string or set through "use
> keyspace" on a connection by client driver.
> There are practical use cases where client user has query and keyspace
> independently. In order for that scenario to work, they will have to create
> one client session per keyspace or have to resort to some string replace
> hackery.
> It will be nice if protocol allowed sending keyspace separately from the
> query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
