[
https://issues.apache.org/jira/browse/FLINK-10997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699548#comment-16699548
]
ASF GitHub Bot commented on FLINK-10997:
----------------------------------------
dawidwys commented on issue #7170: [FLINK-10997][formats] Bundle
kafka-scheme-registry-client
URL: https://github.com/apache/flink/pull/7170#issuecomment-441788027
My understanding/plan when I first worked on it was as @zentol described
that the only dependency user should specify is
`flink-avro-confluent-registry`, but I see also @StephanEwen point that keeping
list of exclusions up-to-date could be fragile. I don't know which one is
better. If we go with the `provided` scope for `flink-avro` we should probably
update the docs that it should be additionally included.
----------------------------------------------------------------
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:
us...@infra.apache.org
> 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)
