cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3707) Add KeyspaceChange CqlResultType
Date Thu, 21 Jun 2012 17:52:43 GMT


paul cannon commented on CASSANDRA-3707:

Yeah, but I'm not sure it's common for client libs to need that information (what keyspace
was used with query Q). The programmer should generally know what keyspace is being used with
a given query.

Do you have a use case?
> Add KeyspaceChange CqlResultType
> --------------------------------
>                 Key: CASSANDRA-3707
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: satish babu krishnamoorthy
>              Labels: cql
>             Fix For: 1.1.2
> 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