[
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-unassigned stale-minor (was:
auto-deprioritized-major auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> 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)
