Re: [PR] KAFKA-20770: LocalLeaderEndPoint should return UNDEFINED_EPOCH when the leader epoch cannot be resolved [kafka]

["SEPURI-SAI-KRISHNA (via GitHub)" <gi...@apache.org>]

SEPURI-SAI-KRISHNA commented on PR #22756:
URL: https://github.com/apache/kafka/pull/22756#issuecomment-5351824552

   Thanks a lot @haung921209, really appreciate you closing #23202 in favor of this one, and the independent verification is genuinely helpful. Your trace through TierStateMachine#buildRemoteLogAuxState and the sweep of the other epochForOffset consumers add useful confidence that the fabricated epoch 0 is confined to these four methods. 
   Thanks again for the collaboration.
   
   This PR has been open since early July, it's a small, self-contained fix (four orElse(0) → orElse(UNDEFINED_EPOCH) in LocalLeaderEndPoint, aligning it with the RemoteLeaderEndPoint/ListOffsets path) plus test coverage, now with independent verification above. @mjsax, you reviewed the related KAFKA-20769 fix recently; would you (or someone you'd suggest) be open to taking a look when convenient? 


-- 
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-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org