I think I understand what you are saying. I think you are saying that perhaps you could break up a given problem into a kind of "system state" and the actual data rows? This is not something we have had a need to do...
-Jay On Thu, Mar 6, 2014 at 12:26 AM, Vjeran Marcinko < vjeran.marci...@email.t-com.hr> wrote: > Thanx Jay, > > Somewhat related to log compaction.... > > Did you have a need at LinkedIn where application should publish 2 messages > on separate topics for each action executed, one to "event data" topic > demarking signalizing executed action, and another one to "state change" > topic which ultimately is good for state replication and can be compacted > after period of time? This state change messages should maybe even contain > reference to event message to be able to see the cause of state change... > > Regards, > Vjeran > > -----Original Message----- > From: Jay Kreps [mailto:jay.kr...@gmail.com] > Sent: Wednesday, March 05, 2014 10:10 PM > To: d...@kafka.apache.org; users@kafka.apache.org > Subject: Documentation for the upcoming 0.8.1 release > > Hey guys, > > I took a stab at updating the docs for the 0.8.1 release. In particular, I > added a section on log compaction: > http://kafka.apache.org/081/documentation.html#compaction > > I also updated the configs. This is all under 081, I will flip this over to > be the main documentation when 0.8.1 is released but you can see it now at > http://kafka.apache.org/081/documentation.html#compaction > > Any comments on improvements we could make would be much appreciated! > > -Jay > >
