[
https://issues.apache.org/jira/browse/BEAM-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285996#comment-17285996
]
Beam JIRA Bot commented on BEAM-11063:
--------------------------------------
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.
> FlinkStateInternals assumes that null value for accumulator means that the
> accumulator was never created
> --------------------------------------------------------------------------------------------------------
>
> Key: BEAM-11063
> URL: https://issues.apache.org/jira/browse/BEAM-11063
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Luke Cwik
> Priority: P2
> Labels: stale-P2
>
> FlinkStateInternals assumes that null value for accumulator means that the
> accumulator was never created. There are combiners which have non-null values
> returned by createAccumulator but null values after merging.
> It would be good to have a ValidatesRunner test that covers an accumulator
> with a null final value and non-null initial value.
> Code link:
> https://github.com/apache/beam/blob/v2.24.0/runners/flink/src/main/java/org/apache/beam/runners/flink/translation/wrappers/streaming/state/FlinkStateInternals.java#L507
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
