Sylvain Lebresne created CASSANDRA-5358:
-------------------------------------------
Summary: Dropping a keyspace does not "delog" existing connections.
Key: CASSANDRA-5358
URL: https://issues.apache.org/jira/browse/CASSANDRA-5358
Project: Cassandra
Issue Type: Bug
Reporter: Sylvain Lebresne
Priority: Minor
Currently, if we drop a keyspace k, this does not reset the "current keyspace"
from the clientState if it is k.
Concretely, this means that if someone drop a keyspace k and then try any query
that doesn't have a fully qualified keyspace, he we get a message "k doesn't
exist" instead of the more user-friendly "you are not logged in any keyspace".
I believe that delogging connections on keyspace drop would be the right thing
to do, but it would probably require tracking open connections more than we do
now. So I'd be fine saying we keep the status quo, but it's important that we
decide which behavior we implement so that client libraries know what to
expect, so I wanted to bring it up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
