divijvaidya commented on PR #14457: URL: https://github.com/apache/kafka/pull/14457#issuecomment-1737266545
> In any case, I think it makes sense to maintain the correct value for lastFetchedEpoch to avoid relying on timing assumptions that may not hold in future. Totally agree. The intention of my comment earlier was to gauge the potential impact of this bug and prevent re-occurrence in future. I completely agree that it should be fixed nevertheless. -- 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