[
https://issues.apache.org/jira/browse/FLINK-30859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703907#comment-17703907
]
Mason Chen commented on FLINK-30859:
------------------------------------
[~martijnvisser] [~tzulitai] [~t...@apache.org] I took at stab at this a while
back and it seems that there are still many components that still rely on the
flink-connector-kafka.
I'll try to enumerate them here:
* confluent-schema-registry-end-to-end-tests
* flink-examples
* flink-examples-build-helper
I think we can consider externalizing the confluent-schema-registry and
confluent-schema-registry-end-to-end-tests since they are closely related to
Kafka.
However, I'm unsure about the examples since users refer to that. If we want to
keep it in the repo, then we need a release of the flink-connector-kafka–I
think we left the earlier release candidate to be expired.
These are just my initial thoughts and I'm happy to start a discussion in the
mailing list if required. Thanks!
> Remove flink-connector-kafka from master branch
> -----------------------------------------------
>
> Key: FLINK-30859
> URL: https://issues.apache.org/jira/browse/FLINK-30859
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Kafka
> Affects Versions: 1.18.0
> Reporter: Mason Chen
> Priority: Major
>
> Remove flink-connector-kafka from master branch since the repo has now been
> externalized and 1.17 commits have been sync'ed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
