[ 
https://issues.apache.org/jira/browse/CASSANDRA-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181592#comment-13181592
 ] 

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: https://issues.apache.org/jira/browse/CASSANDRA-3707
>             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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to