[
https://issues.apache.org/jira/browse/FLINK-20043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228518#comment-17228518
]
Timo Walther commented on FLINK-20043:
--------------------------------------
I guess {{org.javassist:javassist}} and {{javax.xml.bind}} are fine due to the
CDDL part which is [CATEGORY
B|https://www.apache.org/legal/resolved.html#weak-copyleft-licenses].
The SQL jars are not only fat jars but also fat jars that try to avoid
dependency conflicts with other connectors/formats/catalogs. We also removed
the fat jar properties from {{flink-avro-confluent-registry}} recently and
introduced a {{flink-sql-avro-confluent-registry}}. Regular Java/Scala users
should be able to build a Maven/SBT project with dependencies easily themselves.
E.g. I read "Do not relocate guava because it is exposed in the Kinesis API",
this should not apply to a SQL connector because everything is controlled by us.
I would make the decision if we need a dedicated
{{flink-sql-connector-kinesis}} module up to the content of the current Kinesis
jar. Does it include Jackson, Guava, JodaTime?
> Add flink-sql-connector-kinesis package
> ---------------------------------------
>
> Key: FLINK-20043
> URL: https://issues.apache.org/jira/browse/FLINK-20043
> Project: Flink
> Issue Type: Improvement
> Reporter: Alexander Alexandrov
> Assignee: Alexander Alexandrov
> Priority: Major
> Attachments: third-party-report.html
>
>
> This is a follow up item after the recent addition of [Kinesis SQL source and
> sink in PR #13770 |https://github.com/apache/flink/pull/13770].
> Create a package that bundles a fat connector jar that can be used by SQL
> clients. See [FLINK-11026|https://issues.apache.org/jira/browse/FLINK-11026]
> and the related PRs for a discussion how to do that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
