tions
> from
> > > the beginning, and keep polling until all partitions has reached EOF.
> > > > Though, if you have concurrent writers, new messages may be appended
> > > after you observe EOF on a partition, so you are never guaranteed to
> have
> &
you choose to close the consumer.
> > >
> > > /Henning Røigaard-Petersen
> > >
> > > -Original Message-
> > > From: David Espinosa
> > > Sent: 14. september 2018 09:46
> > > To: users@kafka.apache.org
> > > Subject: Best way
gt; -Original Message-
> > From: David Espinosa
> > Sent: 14. september 2018 09:46
> > To: users@kafka.apache.org
> > Subject: Best way for reading all messages and close
> >
> > Hi all,
> >
> > Although the usage of Kafka is stream o
partition, so you are never guaranteed to have read all
> messages at the time you choose to close the consumer.
>
> /Henning Røigaard-Petersen
>
> -Original Message-
> From: David Espinosa
> Sent: 14. september 2018 09:46
> To: users@kafka.apache.org
> Su
messages at the time you choose to close the consumer.
/Henning Røigaard-Petersen
-Original Message-
From: David Espinosa
Sent: 14. september 2018 09:46
To: users@kafka.apache.org
Subject: Best way for reading all messages and close
Hi all,
Although the usage of Kafka is stream oriented
Hi all,
Although the usage of Kafka is stream oriented, for a concrete use case I
need to read all the messages existing in a topic and once all them has
been read then closing the consumer.
What's the best way or framework for doing this?
Thanks in advance,
David,