cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-10145) Change protocol to allow sending key space independent of query string
Date Wed, 12 Apr 2017 18:58:41 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Stupp resolved CASSANDRA-10145.
--------------------------------------
    Resolution: Fixed

Nice work, [~stamhankar999]!

Committed as [1f533260a01552790aff0f5f2f8f2f0aee8dbf10|https://github.com/apache/cassandra/commit/1f533260a01552790aff0f5f2f8f2f0aee8dbf10]
to [trunk|https://github.com/apache/cassandra/tree/trunk]


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

Mime
View raw message