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 <t...@lifelogs.com>: > On Fri, 26 Feb 2010 08:18:49 -0600 Ted Zlatanov <t...@lifelogs.com> wrote: > > TZ> On Tue, 23 Feb 2010 12:30:52 -0600 Ted Zlatanov <t...@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 > >
