[
https://issues.apache.org/jira/browse/FLINK-17083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17083:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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.
> Restrict users of accumulators not to return null in Accumulator#getLocalValue
> ------------------------------------------------------------------------------
>
> Key: FLINK-17083
> URL: https://issues.apache.org/jira/browse/FLINK-17083
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Affects Versions: 1.11.0
> Reporter: Caizhi Weng
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> [This discussion|https://issues.apache.org/jira/browse/FLINK-13880] raises a
> problem that, if a user returns a null value in
> {{Accumulator#getLocalValue}}, he will be notified that the {{failureCause}}
> should not be null when fetching the accumulator result, which seems to be
> really wired.
> The problem is that we're not explicitly restricting the users not to return
> null values in {{Accumulator#getLocalValue}}.
> [~aljoscha] is it legal to return null values? If not, we should explicitly
> throw a related exception to the users instead of giving the users a somewhat
> unrelated exception.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
