cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Shaw (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3707) Add KeyspaceChange CqlResultType
Date Fri, 06 Jan 2012 20:58:39 GMT


Rick Shaw commented on CASSANDRA-3707:

How about returning both current KS and CF in the metadata response on all requests? I understand
it is overhead, but from the clients there is currently no way to get it via CQL.
> Add KeyspaceChange CqlResultType
> --------------------------------
>                 Key: CASSANDRA-3707
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Jonathan Ellis
>            Priority: Minor
>              Labels: cql
>             Fix For: 1.1
> High level clients want to handle failover and load balancing transparently to the application,
which means not just connection pooling but moving an existing connection to another server
if necessary.  When this happens, the client needs to know what the active keyspace was before
failover, so it can set it to the same one in the new connection.
> Currently some clients handle this by checking for "SET KEYSPACE" queries, which violates
the design principle that clients shouldn't have to parse CQL.  Adding a new CqlResultType
(that is set in response to a SET KEYSPACE command) would make this unnecessary.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message