Hey Ido.
I haven't tried to do something like this, but we've worked out some future
plans to do something similar, so I have a bit of interest in what you're
saying.
I feel like there are some details left out from your post. Are your
consumers able to keep up w/ the throughput without the slee
*Hi All,*
*I need a solution to the below Problem statement -*
*How to retrieve only last 1 hour data from an existing Kafka Topic, on 1st
& every consecutive (at every 15 mins interval) of the client application?*
*Note:- The existing Topic is accumulating data since last 6 months.*
*Regards,*
Thanks for the answer, I won't need try-catch around commitSync then. Also
thanks for updating the docs.
2017-09-03 19:47 GMT+02:00 Mickael Maison :
> I believe the Javadoc is slightly incorrect/misleading.
> When it says "offset metadata is too large", it is about the metadata
> you can commit a
I believe the Javadoc is slightly incorrect/misleading.
When it says "offset metadata is too large", it is about the metadata
you can commit along with the offset, not the offset. See
OffsetAndMetadata:
http://kafka.apache.org/0110/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.
The broker and consumer are version 0.11.0.0.
2017-09-03 17:38 GMT+02:00 Jeff Widman :
> What broker version are you testing with?
>
> On Sep 3, 2017 4:14 AM, "Stig Døssing" wrote:
>
> > Hi,
> >
> > The documentation for KafkaConsumer.commitSync(Map) states that a
> > KafkaException will be thro
What broker version are you testing with?
On Sep 3, 2017 4:14 AM, "Stig Døssing" wrote:
> Hi,
>
> The documentation for KafkaConsumer.commitSync(Map) states that a
> KafkaException will be thrown if the committed offset is invalid. I can't
> seem to provoke this behavior, so I'd like clarificati
Hey all.
We are trying to create a controlled lag (a lag of 30 secs). We are doing
that by inspecting a timestamp field for each msg on a specific topic and
doing an actual Thread.sleep for a computed time in the consumer thread
(until the msg is 30 secs old). We were hoping to see that eventually
Hi,
The documentation for KafkaConsumer.commitSync(Map) states that a
KafkaException will be thrown if the committed offset is invalid. I can't
seem to provoke this behavior, so I'd like clarification on whether this is
something the consumer is intended to do.
Here's the snippet I'd expect would
