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
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
