You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/02/20 22:19:39 UTC

[GitHub] [flink] jasoncsinn commented on issue #7170: [FLINK-10997][formats] Bundle kafka-scheme-registry-client

jasoncsinn commented on issue #7170: [FLINK-10997][formats] Bundle kafka-scheme-registry-client
URL: https://github.com/apache/flink/pull/7170#issuecomment-589380340
 
 
   Hi @zentol ,
   
   Sorry to revive an old PR but I was wondering why this artifact shades io.confluent:kafka-schema-registry-client but does not relocate the dependency (as it does with the others).
   
   I have a project which requires a newer version of the schema registry client (5.3.0), but including this artifact in my project causes the calling code to randomly select a client version (the client dependency cannot be explicitly excluded from this artifact as it is shaded, but coincides with the classpath of the newer version). 
   
   If there isn't any particular reason for this, would it be possible to relocate this dependency as well?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services