Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 17 Nov 2016 01:20:58 +0000 (UTC)
From: "Sandeep Tamhankar (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12857633.1440101289000.299526.1479345658410@Atlassian.JIRA>
In-Reply-To: <JIRA.12857633.1440101289000@Atlassian.JIRA>
References: <JIRA.12857633.1440101289000@Atlassian.JIRA> <JIRA.12857633.1440101289917@arcas>
Subject: [jira] [Updated] (CASSANDRA-10145) Change protocol to allow sending
 key space independent of query string
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 17 Nov 2016 01:21:00 -0000


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

Sandeep Tamhankar updated CASSANDRA-10145:
------------------------------------------
    Attachment:     (was: 10145-trunk.txt)

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