You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/02/07 22:38:00 UTC

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

     [ https://issues.apache.org/jira/browse/FLINK-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-3924:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> Remove protobuf shading from Kinesis connector
> ----------------------------------------------
>
>                 Key: FLINK-3924
>                 URL: https://issues.apache.org/jira/browse/FLINK-3924
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Common, Connectors / Kinesis
>            Reporter: Robert Metzger
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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
(v8.20.1#820001)