Thanks for the remarks. hope I didn't miss any.
Not even sure if it makes sense to introduce A and B or just stick with
"this ktable", "other ktable"
Thank you
Jan
On 27.10.2017 06:58, Ted Yu wrote:
Do you mind addressing my previous comments ?
http://search-hadoop.com/m/Kafka/uyzND1hzF8SRz
Thank you Ted, Konstantine. Now I understand. The option 1 worked and if I
produce more records after consumer started, I can see it being returned.
Though option 2 as you described should work but setting auto.offset.reset
to earliest doesn't seems to work and acts like without "--from-beginning"
Please fill in thread link and JIRA number.
* prefix of the output key wich is the same as
serializing K
Typo: wich
* @param joiner
Please add explanation for joiner (in both APIs)
Please add javadoc for valueOtherSerde and joinValueSerde
* an event in this KTabl
Not really.. there are dozens (over 50) producer instances using
librdkafka, it is not feasible to update them all.
I set log.message.timestamp.type to LogAppendTime in server.properties and
it seems to be working (at least --reset-offsets returns the same offset
for the same datetime for partition
Can you update librdkafka and try again ?
Thanks
Original message From: Dan Markhasin
Date: 10/25/17 11:26 PM (GMT-08:00) To: users@kafka.apache.org Subject: Re:
Failure to reset consumer offsets for specific topics
For beats (the topic where timestamps are OK) the producers
