[jira] [Comment Edited] (CASSANDRA-10145) Change protocol to allow sending key space independent of query string

["Sandeep Tamhankar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655891#comment-15655891 ] 

Sandeep Tamhankar edited comment on CASSANDRA-10145 at 11/11/16 2:28 AM:
-------------------------------------------------------------------------

Fully implemented fix for this ticket; added a unit test in MessagePayloadTest.

There are some questions/concerns that I've outlined in native_protocol_v5.spec.

See 10145-trunk.txt, attached to this ticket.


was (Author: stamhankar999):
Fully implemented fix for this ticket; added a unit test in MessagePayloadTest.

There are some questions/concerns that I've outlined in native_protocol_v5.spec.

> 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)