[
https://issues.apache.org/jira/browse/CASSANDRA-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967851#comment-15967851
]
Jeff Jirsa commented on CASSANDRA-10145:
----------------------------------------
[~snazy] [~sandman] - I deleted my comment because I hit submit before I had
finished reading the code. You can still find it if you click the 'all' link in
JIRA, but it's not a big deal. I think the points are valid, but they're not
critical. The style issue is objectively wrong, but it's fairly minor in the
big scheme of things - could be ninja'd certainly. The other two (ctor/ternary)
are just opinions that can be ignored.
> 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
> Labels: client-impacting, protocolv5
> Fix For: 4.0
>
> 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.15#6346)
