See virtual keyspaces in Hector.
Yes, at first, I tried to desigen data model like POD architecture
(http://goo.gl/Uw1yD) with this.
But, it is problem for me that strong consistency isn't guaranteed among
metadata schemas.
Every CF has a certain amount of overhead in memory. It's just not h
why do you think so? I'll let users create ristricted CFs, and limit a
number of CFs which users create.
> is it still a bad one?
>>
> Ok, get it, you want to limit the cf user can create (assume) 2, what
about 10k shared users creating 2 cf each=> 20k CF ~~20GB memory used with
no data in it. Do
> With an abstraction layer you can store practically anything in Cassandra.
See virtual keyspaces in Hector.
> why do you think so? I'll let users create ristricted CFs, and limit a number
> of CFs which users create.
> is it still a bad one?
Depends what your limits are, but in general still y
Every CF has a certain amount of overhead in memory. It's just not how
Cassandra is designed to be used. Maybe you could think of a way to smash
data down to indices and entities. With an abstraction layer you can store
practically anything in Cassandra.
2012/6/5 Toru Inoko
> IMHO a model that a
IMHO a model that allows external users to create CF's is a bad one.
why do you think so? I'll let users create ristricted CFs, and limit a
number of CFs which users create.
is it still a bad one?
On Thu, 31 May 2012 06:44:05 +0900, aaron morton
wrote:
- Do a lot of keyspaces cause some
> - Do a lot of keyspaces cause some problems? (If I have 1,000 users,
> cassandra creates 1,000 keyspaces…)
It's not keyspaces, but the number of column families.
Without storing any data each CF uses about 1MB of ram. When they start storing
and reading data they use more.
IMHO a model that
