Hey Ben. Yes, that's what I'm doing.
If I understand you correctly, you are trying to process the commit
On Tue, Oct 2, 2012 at 2:56 PM, Felipe Schmidt <email@example.com> wrote:
> Seems like the information was dropped or, maybe, not existent in this
> instance of the Schema. But, as soon as I know, it's just one instance of
> the schema in Cassandra, right?
log to get a change list?
If so, then this question has been asked and the general consensus is
that whilst being possible, the commit log is an internal apparatus
subject to change that is not guaranteed to give you the information
you think you should get. Other suggested approaches include producing
your event stream of mutations using AOP or multiplexing change events
on the app layer as they go into Cassandra.