[
https://issues.apache.org/jira/browse/FLINK-40949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124691#comment-18124691
]
Yahya Kisana commented on FLINK-40949:
--------------------------------------
I can take this
> WindowedUnsliceAssigner reports a NULL window bound as "RowTime field should
> not be null."
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-40949
> URL: https://issues.apache.org/jira/browse/FLINK-40949
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.19.3, 2.3.0, 2.2.1, 1.20.5, 2.4.0
> Reporter: Martijn Visser
> Priority: Major
>
> {{UnsliceAssigners.WindowedUnsliceAssigner#createWindow}} throws
> {{RuntimeException("RowTime field should not be null.")}} when window_start
> or window_end of an incoming row is NULL (added with FLINK-34100). The text
> is misleading: this assigner only runs on rows that an upstream window
> operator produced, where both columns are TIMESTAMP(3) NOT NULL, so a NULL
> here means an operator or planner defect and not a NULL in the user's rowtime
> column. {{WatermarkAssignerOperator}} and
> {{SliceAssigners.AbstractSliceAssigner}} use the same text for a NULL rowtime
> attribute, which is a data problem the user can fix, and anything that
> classifies failures by message cannot tell the two apart.
> {{SliceAssigners.WindowedSliceAssigner}} has no null check at all for the
> same situation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
