Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F0E5184CD for ; Thu, 28 Apr 2016 19:51:14 +0000 (UTC) Received: (qmail 53329 invoked by uid 500); 28 Apr 2016 19:51:13 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 53280 invoked by uid 500); 28 Apr 2016 19:51:13 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 52972 invoked by uid 99); 28 Apr 2016 19:51:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Apr 2016 19:51:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 141E32C1F6A for ; Thu, 28 Apr 2016 19:51:13 +0000 (UTC) Date: Thu, 28 Apr 2016 19:51:13 +0000 (UTC) From: "Andy Tolbert (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-11682) 'keyspace' option support on STARTUP message MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andy Tolbert created CASSANDRA-11682: ---------------------------------------- Summary: 'keyspace' option support on STARTUP message Key: CASSANDRA-11682 URL: https://issues.apache.org/jira/browse/CASSANDRA-11682 Project: Cassandra Issue Type: Improvement Reporter: Andy Tolbert Most of the drivers provide a way to bind a keyspace to a Client/Session and subsequently its connections, i.e. in the java-driver: {code} Session session = cluster.connect("mykeyspace"); {code} Currently to bind keyspaces to connections that drivers need to issue a {{USE }} query and keep track of which keyspace is bound to a connection. This is non-trivial to manage and this has been a source of quite a few bugs in the drivers. It would be really nice if in a future protocol version that the {{STARTUP}} message supported an option to provide the keyspace to bind a connection to. This way no separate {{USE }} request needs to be issued. If the keyspace is provided in this way, it could also be a nice consideration to make the keyspace bound to the connection unchangeable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)