You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/30 23:16:01 UTC
[jira] [Updated] (FLINK-21278) NullpointExecption error is reported
when using the evictor method to filter the data before the window
calculation
[ https://issues.apache.org/jira/browse/FLINK-21278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-21278:
-----------------------------------
Labels: auto-deprioritized-critical pull-request-available stale-major (was: auto-deprioritized-critical pull-request-available)
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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> NullpointExecption error is reported when using the evictor method to filter the data before the window calculation
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-21278
> URL: https://issues.apache.org/jira/browse/FLINK-21278
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.12.1
> Reporter: HunterHunter
> Priority: Major
> Labels: auto-deprioritized-critical, pull-request-available, stale-major
>
> When I use evictor() method to filter the data before a window is triggered, if there is no data that meets the conditions, a nullpointExecption error will be reported.
> This problem occurs in the ReduceApplyWindowFunction.apply method.
> So I think if there is no data to calculate whether it can not trigger the calculation, or judge whether it is null before transmitting the calculation result
--
This message was sent by Atlassian Jira
(v8.3.4#803005)