[
https://issues.apache.org/jira/browse/FLINK-14473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu closed FLINK-14473.
---------------------------
Resolution: Won't Fix
> Support nested field as the rowtime attribute
> ---------------------------------------------
>
> Key: FLINK-14473
> URL: https://issues.apache.org/jira/browse/FLINK-14473
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API, Table SQL / Planner
> Reporter: Jark Wu
> Priority: Major
>
> As described in FLIP-66, in theory, the expected rowtime field can be a
> nested field in schema. But this requires a big refactoring for current
> planner, because planner assumes that time attribute can only be top-level,
> and all the time indicator is represented as a single integer.
> All of them need to be refactored, using a new structure to represent the
> position of time attribute, and a generated function to access the time
> attribute.
> Btw, this is not a blocker of FLIP-66, because users can use computed column
> to access the nested fields in DDL to avoid defining a nested time attribute.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
