gt; > Usually
> > > > if
> > > > > you really want #2, requirements #3-6 follow automatically. #5 is
> > > > > potentially a source of much pain if not addressed early on.
> > > > >
> > > > > Pending a response, I would just say solutions
t point means they tend to drop data, generate
> > > > unmatched transactions (orphans), or send things multiple times
> > depending
> > > > on the failure.
> > > >
> > > > It's generally better to design syste
design a transactional sliding window protocol that
> > > works on Kafka.
> > >
> > > Cheers, Robert Hodges
> > >
> > >
> > > On Thu, Jun 5, 2014 at 7:48 AM, Jun Rao wrote:
> > >
> > > > It sounds like that you want to write to a data store and
case that you want to protect is the
> > > client failing btw the two writes. One way to do that is to let the
> > client
> > > publish to Kafka first with the strongest ack. Then, run a few
> consumers
> > to
> > > read data from Kafka and then write the data to the data store. Any one
> &g
sumers
> to
> > read data from Kafka and then write the data to the data store. Any one
> of
> > those consumers can die and the work will be automatically picked up by
> the
> > remaining ones. You can use partition id and the offset of each message
> as
> > its
dn't realize the mailing list wasn't copied...
> >
> >
> > -- Forwarded message --
> > From: Jonathan Hodges
> > Date: Wed, Jun 4, 2014 at 10:56 AM
> > Subject: Re: Hadoop Summit Meetups
> > To: Neha Narkhede
> >
> >
at 10:56 AM, Jonathan Hodges
> > wrote:
> >
> > > Sorry didn't realize the mailing list wasn't copied...
> > >
> > >
> > > -- Forwarded message --
> > > From: Jonathan Hodges
> > > Date: Wed, Jun 4, 2014 at
ing list wasn't copied...
> > >
> > >
> > > -- Forwarded message --
> > > From: Jonathan Hodges
> > > Date: Wed, Jun 4, 2014 at 10:56 AM
> > > Subject: Re: Hadoop Summit Meetups
> > > To: Neha Narkhede
> > &g
un 4, 2014 at 10:56 AM, Jonathan Hodges
> wrote:
>
> > Sorry didn't realize the mailing list wasn't copied...
> >
> >
> > -- Forwarded message --
> > From: Jonathan Hodges
> > Date: Wed, Jun 4, 2014 at 10:56 AM
> > Subjec
UUID if needed.
Thanks,
Jun
On Wed, Jun 4, 2014 at 10:56 AM, Jonathan Hodges wrote:
> Sorry didn't realize the mailing list wasn't copied...
>
>
> -- Forwarded message --
> From: Jonathan Hodges
> Date: Wed, Jun 4, 2014 at 10:56 AM
> Subject: Re: H
Sorry didn't realize the mailing list wasn't copied...
-- Forwarded message --
From: Jonathan Hodges
Date: Wed, Jun 4, 2014 at 10:56 AM
Subject: Re: Hadoop Summit Meetups
To: Neha Narkhede
We have a number of customer facing online learning applications. These
ap
Glad it was useful. It will be great if you can share your requirements on
atomicity. A couple of us are very interested in thinking about
transactional messaging in Kafka.
Thanks,
Neha
On Jun 4, 2014 6:57 AM, "Jonathan Hodges" wrote:
> Hi Neha,
>
> Thanks so much to you and the Kafka team for p
Hi Neha,
Thanks so much to you and the Kafka team for putting together the meetup.
It was very nice and gave people from out of town like us the ability to
join in person.
We are the guys from Pearson Education and we talked a little about
supplying some details on some of our use cases with res
Thanks so much, Neha!
On Fri, Apr 11, 2014 at 10:31 AM, Neha Narkhede wrote:
> Yes, that's a great idea. I can help organize the meetup at LinkedIn.
>
> Thanks,
> Neha
>
>
> On Fri, Apr 11, 2014 at 8:44 AM, Saurabh Agarwal (BLOOMBERG/ 731 LEXIN) <
> sagarwal...@bloomberg.net> wrote:
>
> > great
Yes, that's a great idea. I can help organize the meetup at LinkedIn.
Thanks,
Neha
On Fri, Apr 11, 2014 at 8:44 AM, Saurabh Agarwal (BLOOMBERG/ 731 LEXIN) <
sagarwal...@bloomberg.net> wrote:
> great idea. I am interested in attending as well
>
> - Original Message -
> From: users@ka
With the Hadoop Summit in San Jose 6/3 - 6/5 I wondered if any of the
LinkedIn geniuses were thinking of putting together a meet-up on any of the
associated technologies like Kafka, Samza, Databus, etc. For us poor souls
that don't live on the West Coast it was a great experience attending the
Kaf
16 matches
Mail list logo