cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Stein (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2763) When dropping a keyspace you're currently authenticated to, might be nice to de-authenticate upon completion
Date Tue, 05 Jul 2011 17:15:16 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joe Stein updated CASSANDRA-2763:
---------------------------------

    Attachment: 2763.txt

I made the change to check we were in the keyspace we were deleting before setting it to null.
 This made the most sense to me putting things back in the state you are in when logging into
the CLI and only when you have just deleted the keyspace you were in.

> When dropping a keyspace you're currently authenticated to, might be nice to de-authenticate
upon completion
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2763
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2763
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jeremy Hanna
>            Priority: Trivial
>              Labels: cli, lhf
>         Attachments: 2763.txt
>
>
> I found that when I'm authenticated to MyKeyspace, then do 'drop keyspace MyKeyspace;',
I'm still authenticated to it.  It's trivial I know, but seems reasonable to unauthenticate
from it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message