cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11682) 'keyspace' option support on STARTUP message
Date Fri, 29 Apr 2016 08:44:13 GMT

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

Sylvain Lebresne updated CASSANDRA-11682:
-----------------------------------------
    Labels: protocolv5  (was: )

> '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
>            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
(v6.3.4#6332)

Mime
View raw message