Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
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.