cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Blose (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CASSANDRA-1022) separate assignment of current keyspace from login()
Date Mon, 26 Apr 2010 20:44:33 GMT

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

Todd Blose reassigned CASSANDRA-1022:
-------------------------------------

    Assignee: Todd Blose

> separate assignment of current keyspace from login()
> ----------------------------------------------------
>
>                 Key: CASSANDRA-1022
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1022
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Eric Evans
>            Assignee: Todd Blose
>            Priority: Minor
>
> With the completion of CASSANDRA-714, it is now a requirement that login() be called,
even when using the AllowAllAuthenticator (effectively disabling auth), since this is how
the current/connected keyspace is set. These two disparate functions (assigning keyspace and
authentication) should be disentangled.
> I propose that the keyspace argument be removed from calls to {{login()}}, and that a
new method ({{use_keyspace(string)}}?), be added.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message