Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of 0x6e6562@gmail.com designates
 209.85.216.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAP_qDpzufCfmu350yNVwWn-o5M2i30jy6LgNSMfKgYrxUgWpMg@mail.gmail.com>
References: 
 <CAP_qDpyPyuiKK_JL4v+S7foUp=Z2tvxW-Xt20CiPn4a_Tn4PhA@mail.gmail.com>
	<CAP_qDpzufCfmu350yNVwWn-o5M2i30jy6LgNSMfKgYrxUgWpMg@mail.gmail.com>
Date: Tue, 2 Oct 2012 15:03:02 +0100
Message-ID: 
 <CAB-G1jjSp6hXV+uohVn+G6Nyofh2xj5J9OiLdEin6GYpfAHzYA@mail.gmail.com>
Subject: Re: Getting serialized Rows from CommitLogSegment file
From: Ben Hood <0x6e6562@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Filipe,

On Tue, Oct 2, 2012 at 2:56 PM, Felipe Schmidt <felipefsch@gmail.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?

If I understand you correctly, you are trying to process the commit
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.

HTH,

Ben