becketqin commented on PR #23865: URL: https://github.com/apache/flink/pull/23865#issuecomment-1839717057
@pvary @mbalassi @gaborgsomogyi @JingGe Thanks a lot for the reviews. From what I understand, FLIP-321 does not change the API stability guarantee, it only specifies a migration period. For example. For example, `PublicEvolving` APIs still can be removed with a minor version bump. It is just that with FLIP-321, the removal has to wait for at least an additional minor release. In terms of the source / binary compatibility, the main reason we do not provide binary compatibility in minor releases for any API stability level is because we treat the protocol / format behind the public API as internal. For example, state format might change although the state backend API remains the same. An RPC protocol may change although the APIs in the user library remain the same. In these cases, users don't have to change their code, but they may have to recompile the code or rerun the job, due to the missing binary compatibility. It is not ideal, but it is what we currently do. I agree the compatibility table looks confusing, although the contents seem accurate. I am wondering if some more concrete examples can help here. -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
