[
https://issues.apache.org/jira/browse/CASSANDRA-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672121#comment-15672121
]
Sandeep Tamhankar edited comment on CASSANDRA-10145 at 11/16/16 11:54 PM:
--------------------------------------------------------------------------
After syncing up with [~thobbs], we came to the following conclusions:
* Add an int flags field to PREPARE messages, and make 0x1 mean "has keyspace".
* Rename `ClientState.withKeyspace` to `ClientState.cloneWithKeyspaceIfSet` and
add javadoc comment describing behavior (including with null arg).
* Don't mess with CFStatement.prepareKeyspace variants; both do exist for a
reason.
was (Author: stamhankar999):
After syncing up with [~thobbs], we came to the following conclusions:
* Add an int flags field to PREPARE messages, and make 0x1 mean "has keyspace".
* Rename `ClientState.withKeyspace` to `ClientState.cloneWithKeyspaceIfSet`.
* Don't mess with CFStatement.prepareKeyspace variants; both do exist for a
reason.
> 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)
