Your schema desigin is a RDBMS schema, not a Cassandra schema.
On Thu, Apr 15, 2010 at 11:44 PM, Miguel Verde wrote:
> Just to nitpick your representation a little bit, columnB/etc... are
> supercolumnB/etc..., key1/etc... are column1/etc..., and you can probably
> omit valueA/valueD designations
> OK, I have solved my problems with Cassandra data model. Now I am using
> Column Families of type Super and SuperColumns with many columns inside.
You need to be aware of the third point of
http://wiki.apache.org/cassandra/CassandraLimitations.
That is, super columns are not indexed. Which means
OK, I have solved my problems with Cassandra data model. Now I am using
Column Families of type Super and SuperColumns with many columns inside.
Thanks!
2010/4/16 Julio Carlos Barrera Juez
> Hi again,
>
> First of all, obviously, I have omitted the timestamps to make easy the
> representation,
Hi again,
First of all, obviously, I have omitted the timestamps to make easy the
representation, not in the code. Secondly, there are one supercolumn with
two rows, A and D, all the others are columns, including B,
with various key-values (1, 2, etc.). I need two levels for my design, it is
manda
Just to nitpick your representation a little bit, columnB/etc... are
supercolumnB/etc..., key1/etc... are column1/etc..., and you can probably
omit valueA/valueD designations entirely, it would still be understood.
Columns in Cassandra always have timestamps, you can't omit them.
Can you post a s
Hi all,
I'm working with Cassandra 0.5 and Thrift API. I have a simple doubt:
I want to insert a row in columns inside a supercolumn, like this (without
timestamps):
SuperColumnNameA ==> keyA valueA ==> columnB ==> key1 value1
==> key2 value2
==> key3 value3
