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 2021/02/17 17:16:02 UTC

[jira] [Updated] (BEAM-11063) FlinkStateInternals assumes that null value for accumulator means that the accumulator was never created

     [ https://issues.apache.org/jira/browse/BEAM-11063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Beam JIRA Bot updated BEAM-11063:
---------------------------------
    Labels: stale-P2  (was: )

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