You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:08 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 ]
Beam JIRA Bot updated BEAM-9830:
--------------------------------
Labels: stale-P2 (was: )
> 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
> Priority: P2
> Labels: stale-P2
>
> 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)