You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/02/28 10:57:00 UTC

[jira] [Closed] (FLINK-9461) Disentangle flink-connector-kafka from flink-table and flink-json

     [ https://issues.apache.org/jira/browse/FLINK-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-9461.
--------------------------------
    Resolution: Abandoned

Not sure whether FLIP-32 will ever happen. Due to that I'm closing this issue as abandoned.

> Disentangle flink-connector-kafka from flink-table and flink-json
> -----------------------------------------------------------------
>
>                 Key: FLINK-9461
>                 URL: https://issues.apache.org/jira/browse/FLINK-9461
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Build System
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Priority: Major
>
> Currently, the {{flink-connector-kafka}} module has a dependency on {{flink-table}} and {{flink-json}}. The reason seems to be that the module contains the {{KafkaJsonTableSource}} and {{KafkaJsonTableSink}}. Even though the {{flink-table}} and {{flink-json}} dependency are marked as optional, the {{flink-connector-kafka}} will still contain the table sources and sinks. I think this is not a clean design.
> I would propose to move the table sources and sinks into a dedicated module which depends on {{flink-connector-kafka}}. That way we would better separate dependencies and could remove {{flink-table}} and {{flink-json}} from {{flink-connector-kafka}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)