[ 
https://issues.apache.org/jira/browse/FLINK-20043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17230495#comment-17230495
 ] 

Danny Cranmer commented on FLINK-20043:
---------------------------------------

Most of the Kinesis connector is already shaded and relocated. The following 
dependencies are currently excluded from shaded jar:
- joda-time:joda-time:jar:2.5 (Apache 2.0)
- commons-io:commons-io:jar:2.7 (Apache 2.0)
- commons-lang:commons-lang:jar:2.6 (Apache 2.0)
- commons-logging:commons-logging:jar:1.1.3 (Apache 2.0)
- commons-codec:commons-codec:jar:1.13 (Apache 2.0)
- org.apache.commons:commons-lang3:jar:3.3.2 (Apache 2.0)
- com.google.guava:guava:jar:18.0 (Apache 2.0)
- com.fasterxml.jackson.core:jackson-annotations:jar:2.10.1 (Apache 2.0)
- com.fasterxml.jackson.core:jackson-databind:jar:2.10.1 (Apache 2.0)
- com.fasterxml.jackson.core:jackson-core:jar:2.10.1 (Apache 2.0)
- com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:2.10.1 (Apache 
2.0)
- org.apache.flink:force-shading:jar:1.12-SNAPSHOT

I will shade and relocate the above dependencies, excluding the Flink 
{{force-shading}}. Let me know if any others could be safely excluded if they 
are guaranteed to be available and compatible, provided by the cluster.

I will update the NOTICE and docs accordingly


> 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 and the related PRs for a discussion how to do that.



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

Reply via email to