I think this is a simpler structure, in general, than having every class build up a vector of Thrift Mutations. Since we don't use per-column TTLs or supercolumns, and we don't think of the hierarchy as being row key->column family->column, I think exposing the details of the Thrift model would just clutter up the business logic.

If you agree, I'll comment to that effect.