[
https://issues.apache.org/jira/browse/FLINK-33528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785471#comment-17785471
]
Martijn Visser commented on FLINK-33528:
----------------------------------------
So externalizing the Python connectors would also help protect (given that we
could test against them in the CI) against those type of incompatible changes,
right?
> Externalize Python connector code
> ---------------------------------
>
> Key: FLINK-33528
> URL: https://issues.apache.org/jira/browse/FLINK-33528
> Project: Flink
> Issue Type: Technical Debt
> Components: API / Python, Connectors / Common
> Affects Versions: 1.18.0
> Reporter: Márton Balassi
> Priority: Major
> Fix For: 1.19.0
>
>
> During the connector externalization effort end to end tests for the python
> connectors were left in the main repository under:
> [https://github.com/apache/flink/tree/master/flink-python/pyflink/datastream/connectors]
> These include both python connector implementation and tests. Currently they
> depend on a previously released version of the underlying connectors,
> otherwise they would introduce a circular dependency given that they are in
> the flink repo at the moment.
> This setup prevents us from propagating any breaking change to PublicEvolving
> and Internal APIs used by the connectors as they lead to breaking the python
> e2e tests. We run into this while implementing FLINK-25857.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
