So t= hey are just putted as raw bytes

thx

2012/6/1 aaron morton
If you hash 4 composite keys, let&= #39;s say ('A','B','C'),=A0('A','D'= ,'C'),=A0('A','E','X'),=A0('A','= ;R','X'), you have only 4 hashes or you have more?
Four

but sorry, I don"t= undertand

If you hash 4 composite keys, let's say (= 'A','B','C'),=A0('A','D','C'= ;),=A0('A','E','X'),=A0('A','R',= 9;X'), you have only 4 hashes or you have more?

If it's 4, how come you are able to range query for example betwee= n start_column=3D('A', 'D') and end_column=3D('A',&= #39;E') and get this column ('A','D','C')

the composites are like chapters between the whole keys= set, there must be intermediate keys added?

2012/5/31 aaron morton <aaron@thelastpickle.com= >
it is ha= shed once.=A0

To the partitioner it's just some byte= s. Other parts of the code car about it's structure.=A0

Cheers

<= div style=3D"word-wrap:break-word">
-----------------
Aaron Morton
Freelance Deve= loper
@aaronmorton

On 31/05/2012, at 7:00 PM, Cyril Auburtin wro= te:

1 more thing, a Composite key is not hashed only once I guess?
It's hashed the number of part the composite have?
So this means there are twice or 3 or ... as many keys as for normal column= keys, is it true?

Le 31 mai 2012 02:59, "aaron morton" &= lt;aaron@thela= stpickle.com> a =E9crit=A0:
Composite Columns compare each part in = turn, so the values are ordered as you've shown them.=A0

=
However the rows are not ordered according to key value. They are orde= red using the random token generated by the partitioner see=A0http://wiki.= apache.org/cassandra/FAQ#range_rp

What is the real advanta= ge compared to super column families?
They are = faster.=A0

Cheers

<= div style=3D"word-wrap:break-word">
-----------------
Aaron Morton
Freelance Deve= loper
@aaronmorton

On 29/05/2012, at 10:08 PM, Cyril Auburtin wrote:

How is it done in Cassandra to be able to range que= ry on a composite key?

"key1" =3D> (A:A:C),= =A0(A:B:C),=A0(A:C:C),=A0(A:D:C), (B,A,C)

like get_range ("key1", start_column=3D(A,&qu= ot;), end_column=3D(A, C)); will return [=A0(A:B:C),=A0(A:C:C) ] (in pycass= a)

I mean does the composite implementation add much overh= ead to make it work?
Does it need to add other Column famil= ies, to be able to range query between composites simple keys (first, secon= d and third part of the composite)?

What is the real advantage compared to super column fam= ilies?

"key1" =3D> A: (A,C), (B,C), (= C,C), (D,C) =A0, B: (A,C)

thx

--485b397dd0efe26e7f04c1647e76--