Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "MultiTenant" page has been changed by jeremyhanna. http://wiki.apache.org/cassandra/MultiTenant?action=diff&rev1=15&rev2=16 -------------------------------------------------- = Multi-tenancy with Cassandra = Work is currently being done to support multi-tenant capabilities in Cassandra. This page is meant to list tickets associated with that effort as well as provide some documentation on how multi-tenant clusters can be configured. - == Tickets having to do with multi-tenancy == + == Open tickets having to do with multi-tenancy == - * Basic scheduling based on keyspace - [[https://issues.apache.org/jira/browse/CASSANDRA-1035|CASSANDRA-1035]] + * Better authorization system - [[https://issues.apache.org/jira/browse/CASSANDRA-1271|CASSANDRA-1271]] - * Better authorization system - [[https://issues.apache.org/jira/browse/CASSANDRA-1237|CASSANDRA-1237]], [[https://issues.apache.org/jira/browse/CASSANDRA-1271|CASSANDRA-1271]] * Concurrent schema migrations (multiple users changing schema at once) - [[https://issues.apache.org/jira/browse/CASSANDRA-1391|CASSANDRA-1391]] * Some kind of client transport encryption option. thrift+ssl for clients requires some minimal code for each language - [[https://issues.apache.org/jira/browse/THRIFT-106|THRIFT-106]] is for Java, potential avro ticket - [[https://issues.apache.org/jira/browse/AVRO-341|AVRO-341]] * For multi-tenant order preserved partitioning, auto/online load balancing is pretty important [[https://issues.apache.org/jira/browse/CASSANDRA-1418|CASSANDRA-1418]] * Track per-user/per-keyspace statistics [[https://issues.apache.org/jira/browse/CASSANDRA-841|CASSANDRA-841]] + * Implement a weighted scheduler - e.g. for dev/prod accounts on the same cluster [[https://issues.apache.org/jira/browse/CASSANDRA-1485|CASSANDRA-1485]] + + == Completed tickets having to do with multi-tenancy == + * Dynamic schema changes - [[https://issues.apache.org/jira/browse/CASSANDRA-44|CASSANDRA-44]] + * Basic scheduling based on keyspace - [[https://issues.apache.org/jira/browse/CASSANDRA-1035|CASSANDRA-1035]] + * [[https://issues.apache.org/jira/browse/CASSANDRA-1237|CASSANDRA-1237]] - Store !AccessLevels externally to IAuthenticator (better authorization system) == Ideas under consideration == - * Implement a weighted scheduler - e.g. for dev/prod accounts on the same cluster * Provide relative memory usage settings for caches and Memtables out of configurable (per-user?) totals * Namespaces - in a multi-tenant use case, each user might like to have a keyspace XYZ for whatever reason. So it might be nice to have namespaces so that keyspace XYZ could be specific to their user. Ideally this would be an option that would not affect those that don't use namespaces. * The distinction from keyspaces is that a namespace would be completely transparent to the user: the existence of namespaces would not be exposed. It might be returned by the authentication backend on login, and prefixed to keyspaces transparently.
