nted method to reduce the table overhead to support
>> more tables, but... if you are not expert enough to find it on your own,
>> then you are definitely not expert enough to be using it.
>>
>> -- Jack Krupansky
>>
>> *From:* Raj N
>> *Sent:* Tuesday, Novemb
gt; then you are definitely not expert enough to be using it.
>
> -- Jack Krupansky
>
> *From:* Raj N
> *Sent:* Tuesday, November 25, 2014 12:07 PM
> *To:* user@cassandra.apache.org
> *Subject:* Keyspace and table/cf limits
>
> What's the latest on the maximum number
implementation to determine what
table limit works best for your use case.
-- Jack Krupansky
From: Raj N
Sent: Wednesday, December 3, 2014 4:54 PM
To: user@cassandra.apache.org
Subject: Re: Keyspace and table/cf limits
The question is more from a multi-tenancy point of view. We wanted to see if
25, 2014 12:07 PM
To: user@cassandra.apache.org
Subject: Keyspace and table/cf limits
What's the latest on the maximum number of keyspaces and/or tables that one can
have in Cassandra 2.1.x?
-Raj
On Sat, Dec 6, 2014 at 11:22 AM, Eric Stevens wrote:
> Based on recent conversations with Datastax engineers, the recommendation
> is definitely still to run a finite and reasonable set of column families.
>
> The best way I know of to support multitenancy is to include tenant id in
> all of your
Based on recent conversations with Datastax engineers, the recommendation
is definitely still to run a finite and reasonable set of column families.
The best way I know of to support multitenancy is to include tenant id in
all of your partition keys.
On Fri Dec 05 2014 at 7:39:47 PM Kai Wang wro
On Fri, Dec 5, 2014 at 4:32 PM, Robert Coli wrote:
> On Wed, Dec 3, 2014 at 1:54 PM, Raj N wrote:
>
>> The question is more from a multi-tenancy point of view. We wanted to see
>> if we can have a keyspace per client. Each keyspace may have 50 column
>> families, but if we have 200 clients, that
On Wed, Dec 3, 2014 at 1:54 PM, Raj N wrote:
> The question is more from a multi-tenancy point of view. We wanted to see
> if we can have a keyspace per client. Each keyspace may have 50 column
> families, but if we have 200 clients, that would be 10,000 column families.
> Do you think that's rea
We had the similar problem - multi-tenancy and multiple DC support. But we
did not really have strict requirement of one keyspace per tenant. Our row
keys allow us to put any number of tenants per keyspace.
So, on one side - we could put all data in a single keyspace for all
tenants. And size the
The question is more from a multi-tenancy point of view. We wanted to see
if we can have a keyspace per client. Each keyspace may have 50 column
families, but if we have 200 clients, that would be 10,000 column families.
Do you think that's reasonable to support? I know that key cache capacity
is r
On Tue, Nov 25, 2014 at 9:07 AM, Raj N wrote:
> What's the latest on the maximum number of keyspaces and/or tables that
> one can have in Cassandra 2.1.x?
>
Most relevant changes lately would be :
https://issues.apache.org/jira/browse/CASSANDRA-6689
and
https://issues.apache.org/jira/browse/CAS
What's the latest on the maximum number of keyspaces and/or tables that one
can have in Cassandra 2.1.x?
-Raj
12 matches
Mail list logo
