[ https://issues.apache.org/jira/browse/FLINK-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367445#comment-15367445 ]
Robert Metzger commented on FLINK-3924: --------------------------------------- No. I could not find any good solution for the issue. I've talked with Amazon and they are looking into different approaches. I hope that we can fix the issue for 1.2. For now, we'll need to rely on users building the connector themselves. > Remove protobuf shading from Kinesis connector > ---------------------------------------------- > > Key: FLINK-3924 > URL: https://issues.apache.org/jira/browse/FLINK-3924 > Project: Flink > Issue Type: Sub-task > Components: Kinesis Connector, Streaming Connectors > Reporter: Robert Metzger > Assignee: Robert Metzger > Fix For: 1.2.0 > > > The Kinesis connector is currently creating a fat jar with a custom protobuf > version (2.6.1), relocated into a different package. > We need to build the fat jar to change the protobuf calls from the original > protobuf to the relocated one. > Because Kinesis is licensed under the Amazon Software License (which is not > entirely to the ASL2.0), I don't want to deploy kinesis connector binaries to > maven central with the releases. These binaries would contain code from > Amazon. It would be more than just linking to an (optional) dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)