Thanks for the comment! In my case, I want to store various time slices as indexes, so the content can be serialized as comma-separated concatenation of unique object IDs. Example: on 20101204, multiple clouds experienced a variety of errors in job execution. In addition, multiple users ran (or failed) on different clouds. If I combine user id, cloud id and error code, I can relatively easily drill for errors on a particular date. So each CF maps to a date, and each column in it is a compound index.
-- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-serialized-objects-in-columns-serve-as-ersatz-superCFs-tp6003775p6004834.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
