[
https://issues.apache.org/jira/browse/FLINK-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5105:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Improve ReduceState: value put into ReducingState should always be a copy
> -------------------------------------------------------------------------
>
> Key: FLINK-5105
> URL: https://issues.apache.org/jira/browse/FLINK-5105
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: sunjincheng
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> In case of overlapping sliding windows, multiple references are hold on the
> same object. If we modify value1 or value2 the results are incorrect. The
> value that is put into a ReducingState is always copied. That would allow to
> modify and emit one of the two input values (the one which is comes from the
> state).
> The FoldingState has the same problem.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
