[ 
https://issues.apache.org/jira/browse/FLINK-25363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timo Walther closed FLINK-25363.
--------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

Fixed in master: 6a96044f423b71f61c35cb1f19809a7ddea68a07

> Replace LogicalWindow and related planner expressions
> -----------------------------------------------------
>
>                 Key: FLINK-25363
>                 URL: https://issues.apache.org/jira/browse/FLINK-25363
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / Python, Table SQL / Planner
>            Reporter: Timo Walther
>            Assignee: Francesco Guardiani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> The following classes are legacy from the old Table API.
> {code}
> import org.apache.flink.table.planner.expressions.PlannerNamedWindowProperty;
> import org.apache.flink.table.planner.expressions.PlannerProctimeAttribute;
> import org.apache.flink.table.planner.expressions.PlannerRowtimeAttribute;
> import org.apache.flink.table.planner.expressions.PlannerWindowEnd;
> import org.apache.flink.table.planner.expressions.PlannerWindowProperty;
> import org.apache.flink.table.planner.expressions.PlannerWindowStart;
> import org.apache.flink.table.planner.plan.logical.LogicalWindow;
> import org.apache.flink.table.planner.plan.logical.SessionGroupWindow;
> import org.apache.flink.table.planner.plan.logical.SlidingGroupWindow;
> import org.apache.flink.table.planner.plan.logical.TumblingGroupWindow;
> {code}
> However, currently they are used in {{ExecNode}} and partially are serialized 
> into the JSON plan. Also Python depends on it. Instead we should introduce a 
> small POJO structure with enums. E.g. {{WindowSpec}} with {{WindowProperty}} 
> enum or so. It can be located in the runtime module if Python needs this 
> information during runtime.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to