You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2021/12/17 13:00:00 UTC
[jira] [Created] (FLINK-25363) Replace LogicalWindow and related planner expressions
Timo Walther created FLINK-25363:
------------------------------------
Summary: 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
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)