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

Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2020/04/27 17:13:00 UTC

[jira] [Updated] (BEAM-9830) Flink and Samza pipeline options are incompatible

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

Kyle Weaver updated BEAM-9830:
------------------------------
    Status: Open  (was: Triage Needed)

> Flink and Samza pipeline options are incompatible
> -------------------------------------------------
>
>                 Key: BEAM-9830
>                 URL: https://issues.apache.org/jira/browse/BEAM-9830
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink, runner-samza
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Major
>
> When both the Flink and Samza runners are included in the same application, an exception occurs because they define getMaxBundleSize with different types (long and Long):
> Caused by: java.lang.IllegalArgumentException: methods with same signature getMaxBundleSize() but incompatible return types: long and others
> Originally reported here: https://stackoverflow.com/questions/61441333/conflict-with-runner-dependencies-in-beam



--
This message was sent by Atlassian Jira
(v8.3.4#803005)