I think the idea behind this sentence in storage-conf.xml is just to say that, unless you're doing something specific (like not have the same replication factor for all your data), there is no reason you would want more than one keyspace by application.
As for disadvantages, you may want to know that in the next cassandra release (the 0.7 one), a login will be introduced. With that, the choice of the keyspace will move from every request (as it is right now) to the login part. The following request will then use the keyspace set at login. It may make it a little bit more painful to use multiple keyspace in the same application, so that may be one reason why not to unless you have good reason. -- Sylvain On Tue, Apr 27, 2010 at 3:57 PM, David Boxenhorn <da...@lookin2.com> wrote: > I just saw this note from storage-conf.xml: > > "Except in very unusual circumstances you will have one Keyspace per > application." > > Why is that? > > I was thinking of putting our "normal data" and "indexes" in separate > keyspaces so they could be maintained separately. > > What are the disadvantages of multiple keyspaces?
