[
https://issues.apache.org/jira/browse/CASSANDRA-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291015#comment-13291015
]
Rick Shaw commented on CASSANDRA-3707:
--------------------------------------
Returning in a special type that only gets set when the script calls "USE"
really only tells you what the DEFAULT KS is. Not what KS was used in the
request (other than USE of course). That is because you can say "SELECT x,y
from KS.CF where key="10";" now; where KS can override the currently set
default from USE.
> Add KeyspaceChange CqlResultType
> --------------------------------
>
> Key: CASSANDRA-3707
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3707
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
