Zakelly commented on PR #24636: URL: https://github.com/apache/flink/pull/24636#issuecomment-2047772066
> No that's not the case. In an ideal world, the external connector would only depend on `@Public`, `@PublicEvolving` or `@Experimental` annotated APIs, with the same guarantees. So we could break Public in a new major version, PublicEvolving in a new minor version, Experimental also in patch version. However, we have quite a number of situations where connectors (or users) depend on either `@Internal` interfaces, or those without an annotation. There the question is "Should this actually be a public API" and fix the annotation, or is the connector implementation wrong for relying on an internal API (which is a fair discussion too) Well this makes sense to me. Let's try to fix the wrong annotation or implementation. -- 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
