Hi,
I'm new with Cassandra and I wondering what is the best design for my case.
I have a set of buckets that contain one or thousands of contents.
Here is my Content CF :
CREATE TABLE IF NOT EXISTS contents (tenantID varchar,
key varchar,
type varchar,
bucket varchar,
owner varchar,
workspace varchar,
public_read boolean PRIMARY KEY ((key, tenantID), type, workspace));
To retrieve all contents that belong to a bucket, I have created an index on
the bucket column.
CREATE INDEX IF NOT EXISTS bucket_to_contents ON contents (bucket);
The column value "bucket" is concatenated with the tenantId (bucket =
bucketname+tenantID) in order to avoid filtering on the tenantID on my
application.
Is it the rights way to do or should I create another column family to link
each content to the bucket ?
CREATE TABLE IF NOT EXISTS bucket_to_contents (tenantID varchar,
key varchar,
type varchar,
bucket varchar,
owner varchar,
workspace varchar,
public_read boolean PRIMARY KEY ((bucket, tenantID), key));
Under the hood what is the difference of the both solutions?
According to my understanding, the result will be the same. Both will have the
rowkey equals to the "bucketname" and the "tenantID".
Excepted that the secondary index can have a replication delay...
Can you help me on this point?
Regards,
Eric
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage
exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret
professionnel. Si vous recevez ce message par erreur, merci d'en avertir
imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant
?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre
recherch?e quant au contenu de ce message. Bien que les meilleurs efforts
soient faits pour maintenir cette transmission exempte de tout virus,
l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne
saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, the Worldline liability cannot be triggered for the
message content. Although the sender endeavours to maintain a computer
virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus
transmitted.
