You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Ted Zlatanov <tz...@lifelogs.com> on 2010/03/10 15:16:52 UTC
Re: thinking about dropping hinted handoff
On Fri, 26 Feb 2010 08:18:49 -0600 Ted Zlatanov <tz...@lifelogs.com> wrote:
TZ> On Tue, 23 Feb 2010 12:30:52 -0600 Ted Zlatanov <tz...@lifelogs.com> wrote:
> Can a Cassandra node be made read-only (as far as clients know)?
TZ> I realized I have another use case for read-only access besides backups:
TZ> On our network we have Cassandra readers, writers, and analyzers
TZ> (read+write). The writers and analyzers can run anywhere. The readers
TZ> can run anywhere too. I don't want the readers to have write access but
TZ> they should be able to read all keyspaces.
TZ> I think the best way to solve this is with an IAuthenticator change to
TZ> distinguish between full permissions and read-only permissions. Then
TZ> the Thrift API has to be modified to check for write access in only some
TZ> functions:
...
TZ> Does this seem reasonable?
Any comments, while we're discussing authentication? I think read-only
access makes a lot of sense in this context.
Ted
Re: thinking about dropping hinted handoff
Posted by Ted Zlatanov <tz...@lifelogs.com>.
On Wed, 10 Mar 2010 15:59:55 -0600 Jonathan Ellis <jb...@gmail.com> wrote:
JE> Read-only for a specific client is completely different from trying to
JE> read-only the entire node / cluster. So no, nothing wrong with that.
Cool, thanks. See CASSANDRA-900 for my proposal.
Ted
Re: thinking about dropping hinted handoff
Posted by Jonathan Ellis <jb...@gmail.com>.
Read-only for a specific client is completely different from trying to
read-only the entire node / cluster. So no, nothing wrong with that.
2010/3/10 Ted Zlatanov <tz...@lifelogs.com>:
> On Fri, 26 Feb 2010 08:18:49 -0600 Ted Zlatanov <tz...@lifelogs.com> wrote:
>
> TZ> On Tue, 23 Feb 2010 12:30:52 -0600 Ted Zlatanov <tz...@lifelogs.com> wrote:
>> Can a Cassandra node be made read-only (as far as clients know)?
>
> TZ> I realized I have another use case for read-only access besides backups:
>
> TZ> On our network we have Cassandra readers, writers, and analyzers
> TZ> (read+write). The writers and analyzers can run anywhere. The readers
> TZ> can run anywhere too. I don't want the readers to have write access but
> TZ> they should be able to read all keyspaces.
>
> TZ> I think the best way to solve this is with an IAuthenticator change to
> TZ> distinguish between full permissions and read-only permissions. Then
> TZ> the Thrift API has to be modified to check for write access in only some
> TZ> functions:
> ...
> TZ> Does this seem reasonable?
>
> Any comments, while we're discussing authentication? I think read-only
> access makes a lot of sense in this context.
>
> Ted
>
>
Re: Latest svn code
Posted by Jonathan Ellis <jb...@gmail.com>.
Both.
The latest 0.6 code is in the 0.6 branch.
The latest trunk code (will become 0.7) is in trunk.
Trunk is in "breaking stuff" mode right now.
On Wed, Mar 10, 2010 at 9:50 AM, David Dabbs <dm...@gmail.com> wrote:
> Hi. Is the latest code in trunk or the 0.6 branch?
>
> Thanks,
>
> david
>
>
>
>
Latest svn code
Posted by David Dabbs <dm...@gmail.com>.
Hi. Is the latest code in trunk or the 0.6 branch?
Thanks,
david