CODEWITHSUNDEEP
cassandra
Thor
Thor

Reputation: 650

Cassandra sets or composite columns

I am storing account information in Cassandra. Each account has lists of data associated with it. For example, an account may have a list of friends and a list of liked books. Queries on accounts will always want all friends or all liked books or all of both. No filtering or searching is needed on either. The list of friends and books can grow and shrink.

Is it better to use a set column type or composite columns for this scenario?

Upvotes: 3

Views: 350

Answers (2)

Ananth
Ananth

Reputation: 991

I would suggest you not to use sets if

  1. You are concerned about disk space(as each value is allocated a cell in disk + data space for metadata of each cell which is 15 bytes if am not wrong. Now that consumes a lot if your data is a growing one).

  2. Not going to grow a lot of data in that particular row as each time ,the cells are to be fetched from different sstable .

In these kind of cases, the more preferred option would be a json array. You shall store it as a text and back the data from that.

Set (or any other collections ) use case was brought in for a completely different perspective. If you are having a particular value inside the list or a value has to be updated frequently inside the same collection, you shall make use of the collections .

My take on your query will be this.

Store all account specific info in a json object of friends that has a value as list of books .

Upvotes: 2

Lyuben Todorov
Lyuben Todorov

Reputation: 14173

Sets are good for smaller collections of data, if you expect your friends / liked books lists to grow constantly and get large (there isn't a golden number here) it would be better to go with composite columns as that model scales out better than collections and allows for straight up querying compared to requiring secondary indexes on collections.

Upvotes: 1

Related Questions