[
https://issues.apache.org/jira/browse/BEAM-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121545#comment-17121545
]
Kenneth Knowles commented on BEAM-9830:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: P2
> Labels: stale-assigned
>
> 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)
