mjsax commented on pull request #11233: URL: https://github.com/apache/kafka/pull/11233#issuecomment-903055614
As pointed out on the 3.0 release discussion thread on the dev mailing list, it's really about preserving a clean upgrade path from the old join semantics to the new join semantic. If we just undo the join-fix but keep the API change, how can we enable the join fix later without potentially breaking an existing application? The idea was really, to enable the join-fix if the new API is used: his "forces" users to rewrite their code and to actively opt-in to the new join semantics. -- 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
