You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2017/11/22 14:06:00 UTC

[jira] [Commented] (FLINK-3924) Remove protobuf shading from Kinesis connector

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

Robert Metzger commented on FLINK-3924:
---------------------------------------

I think this will be a problem till Kinesis/Amazon solves the problem.
But I haven't checked recently if they changed something.

> Remove protobuf shading from Kinesis connector
> ----------------------------------------------
>
>                 Key: FLINK-3924
>                 URL: https://issues.apache.org/jira/browse/FLINK-3924
>             Project: Flink
>          Issue Type: Task
>          Components: Kinesis Connector, Streaming Connectors
>            Reporter: Robert Metzger
>
> 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.4.14#64029)