You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 02:32:01 UTC

[jira] [Updated] (CASSANDRA-11682) 'keyspace' option support on STARTUP message

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

C. Scott Andreas updated CASSANDRA-11682:
-----------------------------------------
    Component/s: CQL

> 'keyspace' option support on STARTUP message
> --------------------------------------------
>
>                 Key: CASSANDRA-11682
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11682
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Andy Tolbert
>            Priority: Minor
>              Labels: protocolv5
>
> 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 <keyspace>}} 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 <mykeyspace>}} 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org