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

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-9830:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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)