I am familiar (on a newbie level) with one-to-many modeling using the concept of "wide rows" and composite keys/columns).
E.g. CREATE TABLE (A text, B text, C text static, D text, PRIMARY KEY ((A),B));
This will make Cassandra store data in a wide row and as an effect a one-to-many model can be used. This article explains it quite well:
http://www.ipponusa.com/blog/modeling-data-with-cassandra-what-cql-hides-away-from-you/
Now, lets say I want to model data as an Aggregate Root, to embrace Eric Evans Domain Driven Design concept, to create a transaction boundary around this aggregate root. An example:
An order has order items, this can easily be modelled using the "wide row" concept out-of-the-box using Cassandra's composite keys/column mentioned above. In this model I can put customer info, payment info and, of course, order items as a "one-to-many relation", all stored in one Cassandra row.
However, what if I want the aggregate root to be a little more complex than that? An aggregate root stored in one Cassandra row with two different one-to-many "relations", an example again:
Object A has many B's and A also has many C's. Is it possible to represent this in Cassandra using the "wide row" concept using composite keys/columns and store such "aggregate root" in one row and then be able to fulfill the "transaction boundary" contract?