I am wondering if I should be wary of using types with collections or collections in general. I did read somewhere that it is recommended not to even use collections at all but instead to use multiple columns with denormalized data. Is this true for later Cassandra versions as well?
If it is ok to use collections is there a point where it can be a concern? Like field size?
Small example:
CREATE TYPE IF NOT EXISTS option ( name text ); CREATE TYPE IF NOT EXISTS nested1 ( id text, name text, max_quantity int, options list<FROZEN<option>>, created timestamp, last_updated timestamp ); CREATE TABLE IF NOT EXISTS table1_by_id ( id text, name text, description text, email text, categories set<text>, end_date timestamp, created timestamp, last_updated timestamp, owner_id text, accepted boolean, role text, first_nested list<FROZEN<nested1>>, PRIMARY KEY ((id), email) );
UPDATE: If you don't mind I would like to also expand on my question. Is there a limit to the size of the lists? Or nested collections inside. In the example above, what if I had for example 100 records in the first_nested row? Or a collection on first_nested, what if I had another 100 records on that? Collections greatly simplify query patterns but I am worried that it will cause issues in the future.
