lianetm commented on PR #17440: URL: https://github.com/apache/kafka/pull/17440#issuecomment-2517959270
> Yes, I believe this approach can solve the problem, but it does feel a bit frustrating since we spent quite some time unifying the metadata error propagation method. Perhaps we can create a task later to unify the error propagation behavior of both types of consumers. Well this PR achieved unifying it within the KafkaConsumer, that's a great step! Unifying it between the 2 consumers is a different story, worth exploring but the challenge truly is that the position management is quite different between the 2 (which is the main point of friction we had in the Async consumer, where we needed to detect these failures when updating positions from poll and position, via the same event). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
