[
https://issues.apache.org/jira/browse/BEAM-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248409#comment-17248409
]
Beam JIRA Bot commented on BEAM-11063:
--------------------------------------
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.
> 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
> Assignee: Aljoscha Krettek
> Priority: P2
> Labels: stale-assigned
>
> 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)
