cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Zlatanov (JIRA)" <>
Subject [jira] Reopened: (CASSANDRA-1022) separate assignment of current keyspace from login()
Date Tue, 04 May 2010 14:54:58 GMT


Ted Zlatanov reopened CASSANDRA-1022:

Eric, please remember
where you asked me to merge login() with setKeyspace() and now they are pulled apart again.
 What has changed?  Shouldn't we be insisting on the "one keyspace per connection" concept?
 Or has the philosophy changed?

If set_keyspace() is to be used, it should be the one returning an AccessLevel.  login() should
return void.  In other words, the AccessLevel is per-keyspace, not per-user.

Also, login() should no longer throw AuthorizationException since it doesn't do authorization,
while set_keyspace() should throw it.

Please let me know if I need to implement these changes or if someone else will do it or if
there are any questions.


> separate assignment of current keyspace from login()
> ----------------------------------------------------
>                 Key: CASSANDRA-1022
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Eric Evans
>            Assignee: Todd Blose
>            Priority: Minor
>             Fix For: 0.7
>         Attachments: CASSANDRA-1022.patch
> 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.

View raw message