cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Evans <eev...@rackspace.com>
Subject Re: Cassandra access control
Date Tue, 01 Dec 2009 22:58:50 GMT
On Tue, 2009-12-01 at 15:38 -0600, Ted Zlatanov wrote:
> On Tue, 01 Dec 2009 14:23:47 -0600 Eric Evans <eevans@rackspace.com> wrote: 
> 
> EE> I'm personally not a big fan of the setKeyspace()/getKeyspace() idea.
> EE> Getting rid of the keyspace argument makes sense because the keyspace is
> EE> the highest (or lowest), level of the data-model so its implicit that an
> EE> application need only talk to one. If removing that argument makes sense
> EE> (and I think it does), then we should just do that. Accessing more than
> EE> one keyspace is a corner case IMO, but its one that can be accommodated
> EE> by opening another connection.
> 
> I disagree, why would you want to forbid switching the keyspace?  That's
> turning off a currently working feature.  Also, connections are not
> free, especially across WAN links.

Because it makes a mess out of an API that already confuses people. And
again, I posit that this is a corner case, something that very few
people will actually want to do. We should be optimizing for the common
case.


-- 
Eric Evans
eevans@rackspace.com


Mime
View raw message