[
https://issues.apache.org/jira/browse/FLINK-33941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17800427#comment-17800427
]
Jane Chan commented on FLINK-33941:
-----------------------------------
Thanks, [~xuyangzhong] reporting this issue. You're right that we should rely
on field index rather than field name mapping.
> Use field index instead of field name about window time column
> --------------------------------------------------------------
>
> Key: FLINK-33941
> URL: https://issues.apache.org/jira/browse/FLINK-33941
> Project: Flink
> Issue Type: Technical Debt
> Components: Table SQL / Planner
> Reporter: xuyang
> Priority: Minor
> Labels: pull-request-available
>
> In some exec nodes like StreamExecGroupWindowAggregate and some rules like
> BatchPhysicalWindowAggregateRule, planner uses "AggregateUtil#timeFieldIndex"
> to access the actual time field index, instead of using the time field index
> in LogicalWindow#timeAttribute directly. However, it would be more formal to
> use the field index instead of the column field.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
