[
https://issues.apache.org/jira/browse/FLINK-18213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jackylau updated FLINK-18213:
-----------------------------
Description:
Flink master supports 0.10/0.11/2.x, with three flink-sql-connector shade jar
currently (1.12-snapshot).
As we all know ,kafka client is compatible after 0.10.2.x, so we can use kafka
client 2.x to access to brocker server are 0.10/0.11/2.x.
So we can just use one kafka sql shade jar.
for this , we should do 2 things
1) refactor to 1 shade jar
2) rename flink-kafka-connector mudules with same qualified name in case of
conflicts such as NoSuchMethod or ClassNotFound error
was:
Flink master supports 0.10/0.11/2.x, with three flink-sql-connector shade jar
currently (1.12-snapshot).
As we all know ,kafka client is compatible after 0.10.0.2, so we can use kafka
client 2.x to access to brocker server are 0.10/0.11/2.x.
So we can just use one kafka sql shade jar.
for this , we should do 2 things
1) refactor to 1 shade jar
2) rename flink-kafka-connector mudules with same qualified name in case of
conflicts such as NoSuchMethod or ClassNotFound error
> refactor kafka sql connector to use just one shade to compatible 0.10.0.2 +
> ---------------------------------------------------------------------------
>
> Key: FLINK-18213
> URL: https://issues.apache.org/jira/browse/FLINK-18213
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Affects Versions: 1.11.0
> Reporter: jackylau
> Priority: Major
> Fix For: 1.12.0
>
>
> Flink master supports 0.10/0.11/2.x, with three flink-sql-connector shade jar
> currently (1.12-snapshot).
> As we all know ,kafka client is compatible after 0.10.2.x, so we can use
> kafka client 2.x to access to brocker server are 0.10/0.11/2.x.
> So we can just use one kafka sql shade jar.
> for this , we should do 2 things
> 1) refactor to 1 shade jar
> 2) rename flink-kafka-connector mudules with same qualified name in case of
> conflicts such as NoSuchMethod or ClassNotFound error
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
