Hi Jay,
Eno mentioned that he will narrow down the scope to only ConsumerRecord
deserialisation.
I am working with Database Changelogs only. I would really not like to
see a dead letter queue or something
similliar. how am I expected to get these back in order. Just grind to
hold an call me on the weekend. I'll fix it
then in a few minutes rather spend 2 weeks ordering dead letters. (where
reprocessing might be even the faster fix)
Best Jan
On 29.05.2017 20:23, Jay Kreps wrote:
- I think we should hold off on retries unless we have worked out the
full usage pattern, people can always implement their own. I think the idea
is that you send the message to some kind of dead letter queue and then
replay these later. This obviously destroys all semantic guarantees we are
working hard to provide right now, which may be okay.
