In the cassandra world the best approach is to create on CF with the name and
address in it.
Use a super CF with one super col for the user data and one super col for every
address they have. Pull the entire row back every time you want to read the
data. No need for joins.
Aaron
On 18 Sep
Thanks Paul,
If we make a CF Name_Address(name, address) rather than an index, we have to
maintain it, once any change happens in ID_Address(*Id*, address) ,
Name_ID(*name*, id). Besides, it also occupies some space.
In contrast, if Name_Address(name, address) is just an index, we can
redirect th
Alvin - assuming I understand what you're after correctly, why not make a CF
Name_Address(name, address). Modifying the Cassandra methods to do the "join"
you describe seems like overkill to me...
-Paul
On Sep 15, 2010, at 7:34 PM, Alvin UW wrote:
Hello,
I am going to build an index to join t
Hello,
I am going to build an index to join two CFs.
First, we see this index as a CF/SCF. The difference is I don't materialise
it.
Assume we have two tables:
ID_Address(*Id*, address) , Name_ID(*name*, id)
Then,the index is: Name_Address(*name*, address)
When the application tries to query on
