[
https://issues.apache.org/jira/browse/CASSANDRA-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705684#comment-14705684
]
Tyler Hobbs commented on CASSANDRA-10145:
-----------------------------------------
This wouldn't be usable for prepared statements (the statement has to be
prepared against a known keyspace), so it would only be useful for non-prepared
statements. In general, we prefer to avoid introducing different behaviors for
prepared and non-prepared statements.
Also, in my opinion, using string replacement on non-prepared statements isn't
exactly hacky (that's how the drivers deal with query parameters), so I'm not
sure the small benefit here is worth the work and downsides.
> 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
> Components: Core
> Reporter: Vishy Kasar
>
> 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)
