[
https://issues.apache.org/jira/browse/FLINK-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698303#comment-16698303
]
ASF GitHub Bot commented on FLINK-10997:
----------------------------------------
StephanEwen commented on issue #7170: [FLINK-10997][formats] Bundle
kafka-scheme-registry-client
URL: https://github.com/apache/flink/pull/7170#issuecomment-441473526
+1 to the idea, but we should do it differently.
If you want the Avro dependency not in the shaded jar, simply set it to
provided.
This also automatically drops all transitive dependencies, so no need to
maintain the exclusion list. The exclusion list is cumbersome and fragile,
which seems to be also the reason why travis failed: one missing exclusion
resulting in a collision on the service entries between different jackson
version (one from Avro, other from Schema Registry).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Avro-confluent-registry does not bundle any dependency
> ------------------------------------------------------
>
> Key: FLINK-10997
> URL: https://issues.apache.org/jira/browse/FLINK-10997
> Project: Flink
> Issue Type: Bug
> Components: Formats, Table API & SQL
> Affects Versions: 1.6.2, 1.7.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
>
> The {{flink-avro-confluent-registry}} is not bundling any dependencies, yet
> defines a relocation for the transitive jackson dependency pulled in by
> {{kafka-schema-registry-client}}.
> It is like that the registry-client should be included in the jar.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
