You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by tw...@apache.org on 2021/05/26 10:58:27 UTC

[flink] branch master updated: [FLINK-22740][docs] Drop legacy planner references in docs

This is an automated email from the ASF dual-hosted git repository.

twalthr pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/master by this push:
     new 1e08ed5  [FLINK-22740][docs] Drop legacy planner references in docs
1e08ed5 is described below

commit 1e08ed5e00f0b7f0592d40ba2182f73d5e7b66d5
Author: Timo Walther <tw...@apache.org>
AuthorDate: Fri May 21 11:13:31 2021 +0200

    [FLINK-22740][docs] Drop legacy planner references in docs
    
    This closes #15985.
---
 docs/content.zh/docs/dev/table/legacy_planner.md   | 342 ---------------------
 .../docs/connectors/table/hive/hive_dialect.md     |   4 +-
 .../content/docs/connectors/table/hive/overview.md |   6 +-
 docs/content/docs/connectors/table/jdbc.md         |   2 +-
 .../docs/dev/python/dependency_management.md       |   2 +-
 .../docs/dev/python/table/intro_to_table_api.md    |  20 +-
 .../table/operations/row_based_operations.md       |  10 +-
 .../python/table/python_table_api_connectors.md    |   2 +-
 .../docs/dev/python/table/udfs/python_udfs.md      |  12 +-
 .../python/table/udfs/vectorized_python_udfs.md    |   4 +-
 docs/content/docs/dev/python/table_api_tutorial.md |   4 +-
 docs/content/docs/dev/table/catalogs.md            |   2 +-
 docs/content/docs/dev/table/common.md              |   8 +-
 docs/content/docs/dev/table/legacy_planner.md      | 341 --------------------
 docs/content/docs/dev/table/modules.md             |  12 +-
 docs/content/docs/dev/table/sql/explain.md         |  38 ---
 docs/content/docs/dev/table/tableApi.md            |  35 +--
 17 files changed, 61 insertions(+), 783 deletions(-)

diff --git a/docs/content.zh/docs/dev/table/legacy_planner.md b/docs/content.zh/docs/dev/table/legacy_planner.md
deleted file mode 100644
index 696a8bd..0000000
--- a/docs/content.zh/docs/dev/table/legacy_planner.md
+++ /dev/null
@@ -1,342 +0,0 @@
----
-title: "Legacy Planner"
-weight: 1002
-type: docs
-aliases:
-  - /zh/dev/table/legacy_planner.html
----
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Legacy Planner
-
-Table planners are responsible for translating relational operators into an executable, optimized Flink job.
-Flink supports two different planner implementations; the modern planner (sometimes referred to as `Blink`) and the legacy planner.
-For production use cases, we recommend the modern planner which is the default.
-
-The legacy planner is in maintenance mode and no longer under active development.
-The primary reason to continue using the legacy planner is [DataSet]({{< ref "docs/dev/dataset/overview" >}}) interop.
-
-{{< hint warning >}}
-If you are not using the Legacy planner for DataSet interop, the community strongly
-encourages you to consider the modern table planner. Both batch and stream processing pipelines
-can be expressed in the unified `TableEnvironment`.
-
-** The legacy planner is deprecated and will be dropped in Flink 1.14.**
-{{< /hint >}}
-
-This page describes how to use the Legacy planner and where its semantics differ from the 
-modern planner. 
-
-
-
-## Setup
-
-### Dependencies
-
-When deploying to a cluster, the legacy planner is bundled in Flinks distribution by default.
-If you want to run the Table API & SQL programs locally within your IDE, you must add the
-following set of modules to your application.
-
-```xml
-<dependency>
-  <groupId>org.apache.flink</groupId>
-  <artifactId>flink-table-planner{{< scala_version >}}</artifactId>
-  <version>{{< version >}}</version>
-  <scope>provided</scope>
-</dependency>
-<dependency>
-  <groupId>org.apache.flink</groupId>
-  <artifactId>flink-streaming-scala{{< scala_version >}}</artifactId>
-  <version>{{< version >}}</version>
-  <scope>provided</scope>
-</dependency>
-```
-
-### Configuring the TableEnvironment 
-
-When creating a `TableEnvironment` the Legacy planner is configured via the `EnvironmentSettings`.
-
-{{< tabs "95cbb391-0326-4830-b38e-a5871c87d19f" >}}
-{{< tab "Java" >}}
-```java
-EnvironmentSettings settings = EnvironmentSettings
-    .newInstance()
-    .useOldPlanner()
-    .inStreamingMode()
-    // or in batch mode
-    //.inBatchMode()
-    .build();
-
-TableEnvironment tEnv = TableEnvironment.create(settings);
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```scala
-val settings = EnvironmentSettings
-    .newInstance()
-    .useOldPlanner()
-    .inStreamingMode()
-    // or in batch mode
-    //.inBatchMode()
-    .build()
-
-val tEnv = TableEnvironment.create(settings)
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-`BatchTableEnvironment` may used for [DataSet]({{< ref "docs/dev/dataset/overview" >}}) and [DataStream]({{< ref "docs/dev/datastream/overview" >}}) interop respectively.
-
-{{< tabs "3d8abf94-f59c-4756-a5c0-7b645bf43870" >}}
-{{< tab "Java" >}}
-```java
-ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
-BatchTableEnvironment tEnv = BatchTableEnvironment.create(env);
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```scala
-val env = ExecutionEnvironment.getExecutionEnvironment()
-val tEnv = BatchTableEnvironment.create(env)
-```
-{{< /tab >}}
-{{< tab "Python" >}}
-```python
-from pyflink.dataset import ExecutionEnvironment
-from pyflink.table import BatchTableEnvironment
-
-b_env = ExecutionEnvironment.get_execution_environment()
-t_env = BatchTableEnvironment.create(b_env, table_config)
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-## Integration with DataSet
-
-The primary use case for the Legacy planner is interoperation with the DataSet API. 
-To translate `DataSet`s to and from tables, applications must use the `BatchTableEnvironment`.
-
-### Create a View from a DataSet
-
-A `DataSet` can be registered in a `BatchTableEnvironment` as a `View`.
-The schema of the resulting view depends on the data type of the registered collection.
-
-**Note:** Views created from a `DataSet` can be registered as temporary views only.
-
-{{< tabs "02002c94-df73-4f10-b7b7-6c0f6fbf5909" >}}
-{{< tab "Java" >}}
-```java
-BatchTableEnvironment tEnv = ...; 
-DataSet<Tuple2<Long, String>> dataset = ...;
-
-tEnv.createTemporaryView("my-table", dataset, $("myLong"), $("myString"))
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```java
-val tEnv: BatchTableEnvironment = ??? 
-val dataset: DataSet[(Long, String)] = ???
-
-tEnv.createTemporaryView("my-table", dataset, $"myLong", $"myString")
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-### Create a Table from a DataSet
-
-A `DataSet` can be directly converted to a `Table` in a `BatchTableEnvironment`.
-The schema of the resulting view depends on the data type of the registered collection.
-
-{{< tabs "9bc01f1c-f24c-4be7-9c65-7f6575a12740" >}}
-{{< tab "Java" >}}
-```java
-BatchTableEnvironment tEnv = ...; 
-DataSet<Tuple2<Long, String>> dataset = ...;
-
-Table myTable = tEnv.fromDataSet("my-table", dataset, $("myLong"), $("myString"))
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```java
-val tEnv: BatchTableEnvironment = ??? 
-val dataset: DataSet[(Long, String)] = ???
-
-val table = tEnv.fromDataSet("my-table", dataset, $"myLong", $"myString")
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-### Convert a Table to a DataSet
-
-A `Table` can be converted to a `DataSet`.
-In this way, custom DataSet programs can be run on the result of a Table API or SQL query.
-
-When converting from a `Table`, users must specify the data type of the results.
-Often the most convenient conversion type is `Row`.
-The following list gives an overview of the features of the different options.
-
-- **Row**: fields are mapped by position, arbitrary number of fields, support for `null` values, no type-safe access.
-- **POJO**: fields are mapped by name (POJO fields must be named as `Table` fields), arbitrary number of fields, support for `null` values, type-safe access.
-- **Case Class**: fields are mapped by position, no support for `null` values, type-safe access.
-- **Tuple**: fields are mapped by position, limitation to 22 (Scala) or 25 (Java) fields, no support for `null` values, type-safe access.
-- **Atomic Type**: `Table` must have a single field, no support for `null` values, type-safe access.
-
-{{< tabs "c34bd733-f34e-4780-8cf0-c440465c9f58" >}}
-{{< tab "Java" >}}
-```java
-BatchTableEnvironment tableEnv = BatchTableEnvironment.create(env);
-
-Table table = tableEnv.fromValues(
-    DataTypes.Row(
-        DataTypes.FIELD("name", DataTypes.STRING()),
-        DataTypes.FIELD("age", DataTypes.INT()),
-    row("john", 35),
-    row("sarah", 32));
-
-// Convert the Table into a DataSet of Row by specifying a class
-DataSet<Row> dsRow = tableEnv.toDataSet(table, Row.class);
-
-// Convert the Table into a DataSet of Tuple2<String, Integer> via a TypeInformation
-TupleTypeInfo<Tuple2<String, Integer>> tupleType = new TupleTypeInfo<>(Types.STRING(), Types.INT());
-DataSet<Tuple2<String, Integer>> dsTuple = tableEnv.toDataSet(table, tupleType);
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```scala
-val tableEnv = BatchTableEnvironment.create(env)
-
-val table = tableEnv.fromValues(
-    DataTypes.Row(
-        DataTypes.FIELD("name", DataTypes.STRING()),
-        DataTypes.FIELD("age", DataTypes.INT()),
-    row("john", 35),
-    row("sarah", 32));
-
-// Convert the Table into a DataSet of Row
-val dsRow: DataSet[Row] = tableEnv.toDataSet[Row](table)
-
-// Convert the Table into a DataSet of Tuple2[String, Int]
-val dsTuple: DataSet[(String, Int)] = tableEnv.toDataSet[(String, Int)](table)
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-<span class="label label-danger">Attention</span> **Once the Table is converted to a DataSet, we must use the ExecutionEnvironment.execute method to execute the DataSet program.**
-
-## Data Types
-
-The legacy planner, introduced before Flink 1.9, primarily supports type information.
-It has only limited support for data types.
-It is possible to declare data types that can be translated into type information such that the legacy planner understands them.
-
-The following table summarizes the difference between data type and type information.
-Most simple types, as well as the row type remain the same.
-Time types, array types, and the decimal type need special attention.
-Other hints as the ones mentioned are not allowed.
-
-For the *Type Information* column the table omits the prefix `org.apache.flink.table.api.Types`.
-
-For the *Data Type Representation* column the table omits the prefix `org.apache.flink.table.api.DataTypes`.
-
-| Type Information | Java Expression String | Data Type Representation | Remarks for Data Type |
-|:-----------------|:-----------------------|:-------------------------|:----------------------|
-| `STRING()` | `STRING` | `STRING()` | |
-| `BOOLEAN()` | `BOOLEAN` | `BOOLEAN()` | |
-| `BYTE()` | `BYTE` | `TINYINT()` | |
-| `SHORT()` | `SHORT` | `SMALLINT()` | |
-| `INT()` | `INT` | `INT()` | |
-| `LONG()` | `LONG` | `BIGINT()` | |
-| `FLOAT()` | `FLOAT` | `FLOAT()` | |
-| `DOUBLE()` | `DOUBLE` | `DOUBLE()` | |
-| `ROW(...)` | `ROW<...>` | `ROW(...)` | |
-| `BIG_DEC()` | `DECIMAL` | [`DECIMAL()`] | Not a 1:1 mapping as precision and scale are ignored and Java's variable precision and scale are used. |
-| `SQL_DATE()` | `SQL_DATE` | `DATE()`<br>`.bridgedTo(java.sql.Date.class)` | |
-| `SQL_TIME()` | `SQL_TIME` | `TIME(0)`<br>`.bridgedTo(java.sql.Time.class)` | |
-| `SQL_TIMESTAMP()` | `SQL_TIMESTAMP` | `TIMESTAMP(3)`<br>`.bridgedTo(java.sql.Timestamp.class)` | |
-| `INTERVAL_MONTHS()` | `INTERVAL_MONTHS` | `INTERVAL(MONTH())`<br>`.bridgedTo(Integer.class)` | |
-| `INTERVAL_MILLIS()` | `INTERVAL_MILLIS` | `INTERVAL(DataTypes.SECOND(3))`<br>`.bridgedTo(Long.class)` | |
-| `PRIMITIVE_ARRAY(...)` | `PRIMITIVE_ARRAY<...>` | `ARRAY(DATATYPE.notNull()`<br>`.bridgedTo(PRIMITIVE.class))` | Applies to all JVM primitive types except for `byte`. |
-| `PRIMITIVE_ARRAY(BYTE())` | `PRIMITIVE_ARRAY<BYTE>` | `BYTES()` | |
-| `OBJECT_ARRAY(...)` | `OBJECT_ARRAY<...>` | `ARRAY(`<br>`DATATYPE.bridgedTo(OBJECT.class))` | |
-| `MULTISET(...)` | | `MULTISET(...)` | |
-| `MAP(..., ...)` | `MAP<...,...>` | `MAP(...)` | |
-| other generic types | | `RAW(...)` | |
-
-<span class="label label-danger">Attention</span> If there is a problem with the new type system. Users
-can fallback to type information defined in `org.apache.flink.table.api.Types` at any time.
-
-## Unsupported Features
-
-The following features are not supported by the legacy planner.
-
-- [Deduplication]({{< ref "docs/dev/table/sql/queries" >}}#deduplication %})
-- [Key Value Configurations]({{< ref "docs/dev/table/config" >}}#overview)
-- [Streaming Aggregation Optimization]({{< ref "docs/dev/table/tuning" >}})
-- Streaming mode Grouping sets, Rollup and Cube aggregations
-- [Top-N]({{< ref "docs/dev/table/sql/queries" >}}#top-n)
-- [Versioned Tables]({{< ref "docs/dev/table/concepts/versioned_tables" >}})
-
-## Unsupported Built-In Functions
-
-The following built-in functions are not supported by the legacy planner.
-
-- `PI`
-- `ASCII(string)`
-- `CHR(integer)`
-- `DECODE(binary, string)`
-- `ENCODE(string1, string2)`
-- `INSTR(string1, string2)`
-- `LEFT(string, integer)`
-- `RIGHT(string, integer)`
-- `LOCATE(string1, string2[, integer])`
-- `PARSE_URL(string1, string2[, string3])`
-- `REGEXP(string1, string2)`
-- `REVERSE(string)`
-- `SPLIT_INDEX(string1, string2, integer1)`
-- `STR_TO_MAP(string1[, string2, string3]])`
-- `SUBSTR(string[, integer1[, integer2]])`
-- `CONVERT_TZ(string1, string2, string3)`
-- `FROM_UNIXTIME(numeric[, string])`
-- `UNIX_TIMESTAMP()`
-- `UNIX_TIMESTAMP(string1[, string2])`
-- `TO_DATE(string1[, string2])`
-- `TO_TIMESTAMP(string1[, string2])`
-- `NOW()`
-- `IF(condition, true_value, false_value)`
-- `IS_ALPHA(string)`
-- `IS_DECIMAL(string)`
-- `IS_DIGIT(string)`
-- `VARIANCE([ ALL | DISTINCT ] expression)`
-- `RANK()`
-- `DENSE_RANK()`
-- `ROW_NUMBER()`
-- `LEAD(expression [, offset] [, default] )`
-- `LAG(expression [, offset] [, default])`
-- `FIRST_VALUE(expression)`
-- `LAST_VALUE(expression)`
-- `LISTAGG(expression [, separator])`
-
-{{< hint danger >}}
-`DATE_FORMAT(timestamp, string)` is available in the legacy planner but has serious bugs and should not be used.
-Please implement a custom UDF instead or use `EXTRACT` as a workaround.
-{{< /hint >}}
-
-
-
diff --git a/docs/content/docs/connectors/table/hive/hive_dialect.md b/docs/content/docs/connectors/table/hive/hive_dialect.md
index 47384b5..279267c 100644
--- a/docs/content/docs/connectors/table/hive/hive_dialect.md
+++ b/docs/content/docs/connectors/table/hive/hive_dialect.md
@@ -75,7 +75,7 @@ You can set dialect for your TableEnvironment with Table API.
 {{< tab "Java" >}}
 ```java
 
-EnvironmentSettings settings = EnvironmentSettings.newInstance().useBlinkPlanner()...build();
+EnvironmentSettings settings = EnvironmentSettings.newInstance().build();
 TableEnvironment tableEnv = TableEnvironment.create(settings);
 // to use hive dialect
 tableEnv.getConfig().setSqlDialect(SqlDialect.HIVE);
@@ -88,7 +88,7 @@ tableEnv.getConfig().setSqlDialect(SqlDialect.DEFAULT);
 ```python
 from pyflink.table import *
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 t_env = TableEnvironment.create(settings)
 
 # to use hive dialect
diff --git a/docs/content/docs/connectors/table/hive/overview.md b/docs/content/docs/connectors/table/hive/overview.md
index e8956ec..48e68e1 100644
--- a/docs/content/docs/connectors/table/hive/overview.md
+++ b/docs/content/docs/connectors/table/hive/overview.md
@@ -319,7 +319,7 @@ Following is an example of how to connect to Hive:
 
 ```java
 
-EnvironmentSettings settings = EnvironmentSettings.newInstance().useBlinkPlanner().build();
+EnvironmentSettings settings = EnvironmentSettings.newInstance().build();
 TableEnvironment tableEnv = TableEnvironment.create(settings);
 
 String name            = "myhive";
@@ -337,7 +337,7 @@ tableEnv.useCatalog("myhive");
 
 ```scala
 
-val settings = EnvironmentSettings.newInstance().useBlinkPlanner().build()
+val settings = EnvironmentSettings.newInstance().build()
 val tableEnv = TableEnvironment.create(settings)
 
 val name            = "myhive"
@@ -356,7 +356,7 @@ tableEnv.useCatalog("myhive")
 from pyflink.table import *
 from pyflink.table.catalog import HiveCatalog
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 t_env = TableEnvironment.create(settings)
 
 catalog_name = "myhive"
diff --git a/docs/content/docs/connectors/table/jdbc.md b/docs/content/docs/connectors/table/jdbc.md
index c9eacac..67a41a3 100644
--- a/docs/content/docs/connectors/table/jdbc.md
+++ b/docs/content/docs/connectors/table/jdbc.md
@@ -393,7 +393,7 @@ tableEnv.useCatalog("mypg")
 ```python
 from pyflink.table.catalog import JdbcCatalog
 
-environment_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+environment_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 t_env = TableEnvironment.create(environment_settings)
 
 name = "mypg"
diff --git a/docs/content/docs/dev/python/dependency_management.md b/docs/content/docs/dev/python/dependency_management.md
index 4d5e88f..d215d54 100644
--- a/docs/content/docs/dev/python/dependency_management.md
+++ b/docs/content/docs/dev/python/dependency_management.md
@@ -294,7 +294,7 @@ import org.apache.flink.table.api.EnvironmentSettings;
 import org.apache.flink.table.api.TableEnvironment;
 
 TableEnvironment tEnv = TableEnvironment.create(
-    EnvironmentSettings.newInstance().useBlinkPlanner().inBatchMode().build());
+    EnvironmentSettings.newInstance().inBatchMode().build());
 tEnv.getConfig().getConfiguration().set(CoreOptions.DEFAULT_PARALLELISM, 1);
 
 // register the Python UDF
diff --git a/docs/content/docs/dev/python/table/intro_to_table_api.md b/docs/content/docs/dev/python/table/intro_to_table_api.md
index e16bb53..042d160 100644
--- a/docs/content/docs/dev/python/table/intro_to_table_api.md
+++ b/docs/content/docs/dev/python/table/intro_to_table_api.md
@@ -38,7 +38,7 @@ All Table API and SQL programs, both batch and streaming, follow the same patter
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # 1. create a TableEnvironment
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 # 2. create source Table
@@ -90,11 +90,11 @@ The `TableEnvironment` is a central concept of the Table API and SQL integration
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # create a blink streaming TableEnvironment
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 # or create a blink batch TableEnvironment
-env_settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(env_settings)
 ```
 
@@ -132,7 +132,7 @@ You can create a Table from a list object:
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # create a blink batch TableEnvironment
-env_settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 table = table_env.from_elements([(1, 'Hi'), (2, 'Hello')])
@@ -196,7 +196,7 @@ You can create a Table using connector DDL:
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # create a blink stream TableEnvironment
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 table_env.execute_sql("""
@@ -276,7 +276,7 @@ The following example shows a simple Table API aggregation query:
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # using batch table environment to execute the queries
-env_settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 orders = table_env.from_elements([('Jack', 'FRANCE', 10), ('Rose', 'ENGLAND', 30), ('Jack', 'FRANCE', 20)],
@@ -311,7 +311,7 @@ from pyflink.table.udf import udf
 import pandas as pd
 
 # using batch table environment to execute the queries
-env_settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 orders = table_env.from_elements([('Jack', 'FRANCE', 10), ('Rose', 'ENGLAND', 30), ('Jack', 'FRANCE', 20)],
@@ -347,7 +347,7 @@ The following example shows a simple SQL aggregation query:
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # use a stream TableEnvironment to execute the queries
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 
@@ -607,7 +607,7 @@ The following code shows how to use the `Table.explain()` method:
 # using a stream TableEnvironment
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 table1 = table_env.from_elements([(1, 'Hi'), (2, 'Hello')], ['id', 'data'])
@@ -660,7 +660,7 @@ The following code shows how to use the `StatementSet.explain()` method:
 # using a stream TableEnvironment
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 table1 = table_env.from_elements([(1, 'Hi'), (2, 'Hello')], ['id', 'data'])
diff --git a/docs/content/docs/dev/python/table/operations/row_based_operations.md b/docs/content/docs/dev/python/table/operations/row_based_operations.md
index 846fc96..019c32c 100644
--- a/docs/content/docs/dev/python/table/operations/row_based_operations.md
+++ b/docs/content/docs/dev/python/table/operations/row_based_operations.md
@@ -37,7 +37,7 @@ from pyflink.table import EnvironmentSettings, TableEnvironment
 from pyflink.table.expressions import col
 from pyflink.table.types import DataTypes
 
-env_settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 table = table_env.from_elements([(1, 'Hi'), (2, 'Hello')], ['id', 'data'])
@@ -101,7 +101,7 @@ from pyflink.common import Row
 from pyflink.table.udf import udtf
 from pyflink.table import DataTypes, EnvironmentSettings, TableEnvironment
 
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 table = table_env.from_elements([(1, 'Hi,Flink'), (2, 'Hello')], ['id', 'data'])
@@ -181,7 +181,7 @@ agg = udaf(function,
 
 # aggregate with a python general aggregate function
 
-env_settings = EnvironmentSettings.new_instance().in_streaming_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 t = table_env.from_elements([(1, 2), (2, 1), (1, 3)], ['a', 'b'])
 
@@ -196,7 +196,7 @@ result.to_pandas()
 # 1  2  1  1
 
 # aggregate with a python vectorized aggregate function
-env_settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(env_settings)
 
 t = table_env.from_elements([(1, 2), (2, 1), (1, 3)], ['a', 'b'])
@@ -256,7 +256,7 @@ class Top2(TableAggregateFunction):
             [DataTypes.FIELD("a", DataTypes.BIGINT())])
 
 
-env_settings = EnvironmentSettings.new_instance().use_blink_planner().in_streaming_mode().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 # the result type and accumulator type can also be specified in the udtaf decorator:
 # top2 = udtaf(Top2(), result_type=DataTypes.ROW([DataTypes.FIELD("a", DataTypes.BIGINT())]), accumulator_type=DataTypes.ARRAY(DataTypes.BIGINT()))
diff --git a/docs/content/docs/dev/python/table/python_table_api_connectors.md b/docs/content/docs/dev/python/table/python_table_api_connectors.md
index 4c473a6..f796025 100644
--- a/docs/content/docs/dev/python/table/python_table_api_connectors.md
+++ b/docs/content/docs/dev/python/table/python_table_api_connectors.md
@@ -86,7 +86,7 @@ Below is a complete example of how to use a Kafka source/sink and the JSON forma
 from pyflink.table import TableEnvironment, EnvironmentSettings
 
 def log_processing():
-    env_settings = EnvironmentSettings.new_instance().use_blink_planner().is_streaming_mode().build()
+    env_settings = EnvironmentSettings.new_instance().is_streaming_mode().build()
     t_env = TableEnvironment.create(env_settings)
     # specify connector and format jars
     t_env.get_config().get_configuration().set_string("pipeline.jars", "file:///my/jar/path/connector.jar;file:///my/jar/path/json.jar")
diff --git a/docs/content/docs/dev/python/table/udfs/python_udfs.md b/docs/content/docs/dev/python/table/udfs/python_udfs.md
index ab31719..abc1291 100644
--- a/docs/content/docs/dev/python/table/udfs/python_udfs.md
+++ b/docs/content/docs/dev/python/table/udfs/python_udfs.md
@@ -50,7 +50,7 @@ class HashCode(ScalarFunction):
   def eval(self, s):
     return hash(s) * self.factor
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(settings)
 
 hash_code = udf(HashCode(), result_type=DataTypes.BIGINT())
@@ -80,7 +80,7 @@ public class HashCode extends ScalarFunction {
 '''
 from pyflink.table.expressions import call
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(settings)
 
 # register the Java function
@@ -150,7 +150,7 @@ class Split(TableFunction):
         for s in string.split(" "):
             yield s, len(s)
 
-env_settings = EnvironmentSettings.new_instance().use_blink_planner().is_streaming_mode().build()
+env_settings = EnvironmentSettings.new_instance().is_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 my_table = ...  # type: Table, table schema: [a: String]
 
@@ -188,7 +188,7 @@ public class Split extends TableFunction<Tuple2<String, Integer>> {
 '''
 from pyflink.table.expressions import call
 
-env_settings = EnvironmentSettings.new_instance().use_blink_planner().is_streaming_mode().build()
+env_settings = EnvironmentSettings.new_instance().is_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 my_table = ...  # type: Table, table schema: [a: String]
 
@@ -302,7 +302,7 @@ class WeightedAvg(AggregateFunction):
             DataTypes.FIELD("f1", DataTypes.BIGINT())])
 
 
-env_settings = EnvironmentSettings.new_instance().use_blink_planner().is_streaming_mode().build()
+env_settings = EnvironmentSettings.new_instance().is_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 # the result type and accumulator type can also be specified in the udaf decorator:
 # weighted_avg = udaf(WeightedAvg(), result_type=DataTypes.BIGINT(), accumulator_type=...)
@@ -477,7 +477,7 @@ class Top2(TableAggregateFunction):
             [DataTypes.FIELD("a", DataTypes.BIGINT())])
 
 
-env_settings = EnvironmentSettings.new_instance().use_blink_planner().in_streaming_mode().build()
+env_settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 table_env = TableEnvironment.create(env_settings)
 # the result type and accumulator type can also be specified in the udtaf decorator:
 # top2 = udtaf(Top2(), result_type=DataTypes.ROW([DataTypes.FIELD("a", DataTypes.BIGINT())]), accumulator_type=DataTypes.ARRAY(DataTypes.BIGINT()))
diff --git a/docs/content/docs/dev/python/table/udfs/vectorized_python_udfs.md b/docs/content/docs/dev/python/table/udfs/vectorized_python_udfs.md
index 0fb19ad..f45bdae 100644
--- a/docs/content/docs/dev/python/table/udfs/vectorized_python_udfs.md
+++ b/docs/content/docs/dev/python/table/udfs/vectorized_python_udfs.md
@@ -53,7 +53,7 @@ and use it in a query:
 def add(i, j):
   return i + j
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(settings)
 
 # use the vectorized Python scalar function in Python Table API
@@ -86,7 +86,7 @@ and use it in `GroupBy Aggregation`, `GroupBy Window Aggregation` and `Over Wind
 def mean_udaf(v):
     return v.mean()
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 table_env = TableEnvironment.create(settings)
 
 my_table = ...  # type: Table, table schema: [a: String, b: BigInt, c: BigInt]
diff --git a/docs/content/docs/dev/python/table_api_tutorial.md b/docs/content/docs/dev/python/table_api_tutorial.md
index 49fdbd4..d92804f 100644
--- a/docs/content/docs/dev/python/table_api_tutorial.md
+++ b/docs/content/docs/dev/python/table_api_tutorial.md
@@ -69,7 +69,7 @@ It can be used for setting execution parameters such as restart strategy, defaul
 The table config allows setting Table API specific configurations.
 
 ```python
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 t_env = TableEnvironment.create(settings)
 ```
 
@@ -147,7 +147,7 @@ from pyflink.table import DataTypes, TableEnvironment, EnvironmentSettings
 from pyflink.table.descriptors import Schema, OldCsv, FileSystem
 from pyflink.table.expressions import lit
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 t_env = TableEnvironment.create(settings)
 
 # write all the data to one file
diff --git a/docs/content/docs/dev/table/catalogs.md b/docs/content/docs/dev/table/catalogs.md
index 3249a0a..7c65017 100644
--- a/docs/content/docs/dev/table/catalogs.md
+++ b/docs/content/docs/dev/table/catalogs.md
@@ -245,7 +245,7 @@ from pyflink.table import *
 from pyflink.table.catalog import HiveCatalog, CatalogDatabase, ObjectPath, CatalogBaseTable
 from pyflink.table.descriptors import Kafka
 
-settings = EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().in_batch_mode().build()
 t_env = TableEnvironment.create(settings)
 
 # Create a HiveCatalog
diff --git a/docs/content/docs/dev/table/common.md b/docs/content/docs/dev/table/common.md
index 5872ba1..be7be3e 100644
--- a/docs/content/docs/dev/table/common.md
+++ b/docs/content/docs/dev/table/common.md
@@ -161,7 +161,7 @@ val tEnv = TableEnvironment.create(setting)
 from pyflink.table import EnvironmentSettings, TableEnvironment
 
 # create a blink streaming TableEnvironment
-env_settings = EnvironmentSettings.new_instance().use_blink_planner().build()
+env_settings = EnvironmentSettings.new_instance().build()
 table_env = TableEnvironment.create(env_settings)
 
 # create a blink batch TableEnvironment
@@ -841,7 +841,7 @@ The following code shows an example and the corresponding output for multiple-si
 {{< tab "Java" >}}
 ```java
 
-EnvironmentSettings settings = EnvironmentSettings.newInstance().useBlinkPlanner().inStreamingMode().build();
+EnvironmentSettings settings = EnvironmentSettings.newInstance().inStreamingMode().build();
 TableEnvironment tEnv = TableEnvironment.create(settings);
 
 final Schema schema = new Schema()
@@ -880,7 +880,7 @@ System.out.println(explanation);
 {{< /tab >}}
 {{< tab "Scala" >}}
 ```scala
-val settings = EnvironmentSettings.newInstance.useBlinkPlanner.inStreamingMode.build
+val settings = EnvironmentSettings.newInstance.inStreamingMode.build
 val tEnv = TableEnvironment.create(settings)
 
 val schema = new Schema()
@@ -919,7 +919,7 @@ println(explanation)
 {{< /tab >}}
 {{< tab "Python" >}}
 ```python
-settings = EnvironmentSettings.new_instance().use_blink_planner().in_streaming_mode().build()
+settings = EnvironmentSettings.new_instance().in_streaming_mode().build()
 t_env = TableEnvironment.create(environment_settings=settings)
 
 schema = Schema()
diff --git a/docs/content/docs/dev/table/legacy_planner.md b/docs/content/docs/dev/table/legacy_planner.md
deleted file mode 100644
index 72b2199..0000000
--- a/docs/content/docs/dev/table/legacy_planner.md
+++ /dev/null
@@ -1,341 +0,0 @@
----
-title: "Legacy Planner"
-weight: 1002
-type: docs
-aliases:
-  - /dev/table/legacy_planner.html
----
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Legacy Planner
-
-Table planners are responsible for translating relational operators into an executable, optimized Flink job.
-Flink supports two different planner implementations; the modern planner (sometimes referred to as `Blink`) and the legacy planner.
-For production use cases, we recommend the modern planner which is the default.
-
-The legacy planner is in maintenance mode and no longer under active development.
-The primary reason to continue using the legacy planner is [DataSet]({{< ref "docs/dev/dataset/overview" >}}) interop.
-
-{{< hint warning >}}
-If you are not using the Legacy planner for DataSet interop, the community strongly
-encourages you to consider the modern table planner. Both batch and stream processing pipelines
-can be expressed in the unified `TableEnvironment`.
-
-** The legacy planner is deprecated and will be dropped in Flink 1.14.**
-{{< /hint >}}
-
-This page describes how to use the Legacy planner and where its semantics differ from the 
-modern planner. 
-
-
-
-## Setup
-
-### Dependencies
-
-When deploying to a cluster, the legacy planner is bundled in Flinks distribution by default.
-If you want to run the Table API & SQL programs locally within your IDE, you must add the
-following set of modules to your application.
-
-```xml
-<dependency>
-  <groupId>org.apache.flink</groupId>
-  <artifactId>flink-table-planner{{< scala_version >}}</artifactId>
-  <version>{{< version >}}</version>
-  <scope>provided</scope>
-</dependency>
-<dependency>
-  <groupId>org.apache.flink</groupId>
-  <artifactId>flink-streaming-scala{{< scala_version >}}</artifactId>
-  <version>{{< version >}}</version>
-  <scope>provided</scope>
-</dependency>
-```
-
-### Configuring the TableEnvironment 
-
-When creating a `TableEnvironment` the Legacy planner is configured via the `EnvironmentSettings`.
-
-{{< tabs "95cbb391-0326-4830-b38e-a5871c87d19f" >}}
-{{< tab "Java" >}}
-```java
-EnvironmentSettings settings = EnvironmentSettings
-    .newInstance()
-    .useOldPlanner()
-    .inStreamingMode()
-    // or in batch mode
-    //.inBatchMode()
-    .build();
-
-TableEnvironment tEnv = TableEnvironment.create(settings);
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```scala
-val settings = EnvironmentSettings
-    .newInstance()
-    .useOldPlanner()
-    .inStreamingMode()
-    // or in batch mode
-    //.inBatchMode()
-    .build()
-
-val tEnv = TableEnvironment.create(settings)
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-`BatchTableEnvironment` may used for [DataSet]({{< ref "docs/dev/dataset/overview" >}}) and [DataStream]({{< ref "docs/dev/datastream/overview" >}}) interop respectively.
-
-{{< tabs "3d8abf94-f59c-4756-a5c0-7b645bf43870" >}}
-{{< tab "Java" >}}
-```java
-ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
-BatchTableEnvironment tEnv = BatchTableEnvironment.create(env);
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```scala
-val env = ExecutionEnvironment.getExecutionEnvironment()
-val tEnv = BatchTableEnvironment.create(env)
-```
-{{< /tab >}}
-{{< tab "Python" >}}
-```python
-from pyflink.dataset import ExecutionEnvironment
-from pyflink.table import BatchTableEnvironment
-
-b_env = ExecutionEnvironment.get_execution_environment()
-t_env = BatchTableEnvironment.create(b_env, table_config)
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-## Integration with DataSet
-
-The primary use case for the Legacy planner is interoperation with the DataSet API. 
-To translate `DataSet`s to and from tables, applications must use the `BatchTableEnvironment`.
-
-### Create a View from a DataSet
-
-A `DataSet` can be registered in a `BatchTableEnvironment` as a `View`.
-The schema of the resulting view depends on the data type of the registered collection.
-
-**Note:** Views created from a `DataSet` can be registered as temporary views only.
-
-{{< tabs "02002c94-df73-4f10-b7b7-6c0f6fbf5909" >}}
-{{< tab "Java" >}}
-```java
-BatchTableEnvironment tEnv = ...; 
-DataSet<Tuple2<Long, String>> dataset = ...;
-
-tEnv.createTemporaryView("my-table", dataset, $("myLong"), $("myString"))
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```java
-val tEnv: BatchTableEnvironment = ??? 
-val dataset: DataSet[(Long, String)] = ???
-
-tEnv.createTemporaryView("my-table", dataset, $"myLong", $"myString")
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-### Create a Table from a DataSet
-
-A `DataSet` can be directly converted to a `Table` in a `BatchTableEnvironment`.
-The schema of the resulting view depends on the data type of the registered collection.
-
-{{< tabs "9bc01f1c-f24c-4be7-9c65-7f6575a12740" >}}
-{{< tab "Java" >}}
-```java
-BatchTableEnvironment tEnv = ...; 
-DataSet<Tuple2<Long, String>> dataset = ...;
-
-Table myTable = tEnv.fromDataSet("my-table", dataset, $("myLong"), $("myString"))
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```java
-val tEnv: BatchTableEnvironment = ??? 
-val dataset: DataSet[(Long, String)] = ???
-
-val table = tEnv.fromDataSet("my-table", dataset, $"myLong", $"myString")
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-### Convert a Table to a DataSet
-
-A `Table` can be converted to a `DataSet`.
-In this way, custom DataSet programs can be run on the result of a Table API or SQL query.
-
-When converting from a `Table`, users must specify the data type of the results.
-Often the most convenient conversion type is `Row`.
-The following list gives an overview of the features of the different options.
-
-- **Row**: fields are mapped by position, arbitrary number of fields, support for `null` values, no type-safe access.
-- **POJO**: fields are mapped by name (POJO fields must be named as `Table` fields), arbitrary number of fields, support for `null` values, type-safe access.
-- **Case Class**: fields are mapped by position, no support for `null` values, type-safe access.
-- **Tuple**: fields are mapped by position, limitation to 22 (Scala) or 25 (Java) fields, no support for `null` values, type-safe access.
-- **Atomic Type**: `Table` must have a single field, no support for `null` values, type-safe access.
-
-{{< tabs "c34bd733-f34e-4780-8cf0-c440465c9f58" >}}
-{{< tab "Java" >}}
-```java
-BatchTableEnvironment tableEnv = BatchTableEnvironment.create(env);
-
-Table table = tableEnv.fromValues(
-    DataTypes.Row(
-        DataTypes.FIELD("name", DataTypes.STRING()),
-        DataTypes.FIELD("age", DataTypes.INT()),
-    row("john", 35),
-    row("sarah", 32));
-
-// Convert the Table into a DataSet of Row by specifying a class
-DataSet<Row> dsRow = tableEnv.toDataSet(table, Row.class);
-
-// Convert the Table into a DataSet of Tuple2<String, Integer> via a TypeInformation
-TupleTypeInfo<Tuple2<String, Integer>> tupleType = new TupleTypeInfo<>(Types.STRING(), Types.INT());
-DataSet<Tuple2<String, Integer>> dsTuple = tableEnv.toDataSet(table, tupleType);
-```
-{{< /tab >}}
-{{< tab "Scala" >}}
-```scala
-val tableEnv = BatchTableEnvironment.create(env)
-
-val table = tableEnv.fromValues(
-    DataTypes.Row(
-        DataTypes.FIELD("name", DataTypes.STRING()),
-        DataTypes.FIELD("age", DataTypes.INT()),
-    row("john", 35),
-    row("sarah", 32));
-
-// Convert the Table into a DataSet of Row
-val dsRow: DataSet[Row] = tableEnv.toDataSet[Row](table)
-
-// Convert the Table into a DataSet of Tuple2[String, Int]
-val dsTuple: DataSet[(String, Int)] = tableEnv.toDataSet[(String, Int)](table)
-```
-{{< /tab >}}
-{{< /tabs >}}
-
-<span class="label label-danger">Attention</span> **Once the Table is converted to a DataSet, we must use the ExecutionEnvironment.execute method to execute the DataSet program.**
-
-## Data Types
-
-The legacy planner, introduced before Flink 1.9, primarily supports type information.
-It has only limited support for data types.
-It is possible to declare data types that can be translated into type information such that the legacy planner understands them.
-
-The following table summarizes the difference between data type and type information.
-Most simple types, as well as the row type remain the same.
-Time types, array types, and the decimal type need special attention.
-Other hints as the ones mentioned are not allowed.
-
-For the *Type Information* column the table omits the prefix `org.apache.flink.table.api.Types`.
-
-For the *Data Type Representation* column the table omits the prefix `org.apache.flink.table.api.DataTypes`.
-
-| Type Information | Java Expression String | Data Type Representation | Remarks for Data Type |
-|:-----------------|:-----------------------|:-------------------------|:----------------------|
-| `STRING()` | `STRING` | `STRING()` | |
-| `BOOLEAN()` | `BOOLEAN` | `BOOLEAN()` | |
-| `BYTE()` | `BYTE` | `TINYINT()` | |
-| `SHORT()` | `SHORT` | `SMALLINT()` | |
-| `INT()` | `INT` | `INT()` | |
-| `LONG()` | `LONG` | `BIGINT()` | |
-| `FLOAT()` | `FLOAT` | `FLOAT()` | |
-| `DOUBLE()` | `DOUBLE` | `DOUBLE()` | |
-| `ROW(...)` | `ROW<...>` | `ROW(...)` | |
-| `BIG_DEC()` | `DECIMAL` | [`DECIMAL()`] | Not a 1:1 mapping as precision and scale are ignored and Java's variable precision and scale are used. |
-| `SQL_DATE()` | `SQL_DATE` | `DATE()`<br>`.bridgedTo(java.sql.Date.class)` | |
-| `SQL_TIME()` | `SQL_TIME` | `TIME(0)`<br>`.bridgedTo(java.sql.Time.class)` | |
-| `SQL_TIMESTAMP()` | `SQL_TIMESTAMP` | `TIMESTAMP(3)`<br>`.bridgedTo(java.sql.Timestamp.class)` | |
-| `INTERVAL_MONTHS()` | `INTERVAL_MONTHS` | `INTERVAL(MONTH())`<br>`.bridgedTo(Integer.class)` | |
-| `INTERVAL_MILLIS()` | `INTERVAL_MILLIS` | `INTERVAL(DataTypes.SECOND(3))`<br>`.bridgedTo(Long.class)` | |
-| `PRIMITIVE_ARRAY(...)` | `PRIMITIVE_ARRAY<...>` | `ARRAY(DATATYPE.notNull()`<br>`.bridgedTo(PRIMITIVE.class))` | Applies to all JVM primitive types except for `byte`. |
-| `PRIMITIVE_ARRAY(BYTE())` | `PRIMITIVE_ARRAY<BYTE>` | `BYTES()` | |
-| `OBJECT_ARRAY(...)` | `OBJECT_ARRAY<...>` | `ARRAY(`<br>`DATATYPE.bridgedTo(OBJECT.class))` | |
-| `MULTISET(...)` | | `MULTISET(...)` | |
-| `MAP(..., ...)` | `MAP<...,...>` | `MAP(...)` | |
-| other generic types | | `RAW(...)` | |
-
-<span class="label label-danger">Attention</span> If there is a problem with the new type system. Users
-can fallback to type information defined in `org.apache.flink.table.api.Types` at any time.
-
-## Unsupported Features
-
-The following features are not supported by the legacy planner.
-
-- [Deduplication]({{< ref "docs/dev/table/sql/queries" >}}#deduplication %})
-- [Key Value Configurations]({{< ref "docs/dev/table/config" >}}#overview)
-- [Streaming Aggregation Optimization]({{< ref "docs/dev/table/tuning" >}})
-- Streaming mode Grouping sets, Rollup and Cube aggregations
-- [Top-N]({{< ref "docs/dev/table/sql/queries" >}}#top-n)
-- [Versioned Tables]({{< ref "docs/dev/table/concepts/versioned_tables" >}})
-
-## Unsupported Built-In Functions
-
-The following built-in functions are not supported by the legacy planner.
-
-- `PI`
-- `ASCII(string)`
-- `CHR(integer)`
-- `DECODE(binary, string)`
-- `ENCODE(string1, string2)`
-- `INSTR(string1, string2)`
-- `LEFT(string, integer)`
-- `RIGHT(string, integer)`
-- `LOCATE(string1, string2[, integer])`
-- `PARSE_URL(string1, string2[, string3])`
-- `REGEXP(string1, string2)`
-- `REVERSE(string)`
-- `SPLIT_INDEX(string1, string2, integer1)`
-- `STR_TO_MAP(string1[, string2, string3]])`
-- `SUBSTR(string[, integer1[, integer2]])`
-- `CONVERT_TZ(string1, string2, string3)`
-- `FROM_UNIXTIME(numeric[, string])`
-- `UNIX_TIMESTAMP()`
-- `UNIX_TIMESTAMP(string1[, string2])`
-- `TO_DATE(string1[, string2])`
-- `TO_TIMESTAMP(string1[, string2])`
-- `NOW()`
-- `IF(condition, true_value, false_value)`
-- `IS_ALPHA(string)`
-- `IS_DECIMAL(string)`
-- `IS_DIGIT(string)`
-- `VARIANCE([ ALL | DISTINCT ] expression)`
-- `RANK()`
-- `DENSE_RANK()`
-- `ROW_NUMBER()`
-- `LEAD(expression [, offset] [, default] )`
-- `LAG(expression [, offset] [, default])`
-- `FIRST_VALUE(expression)`
-- `LAST_VALUE(expression)`
-- `LISTAGG(expression [, separator])`
-
-{{< hint danger >}}
-`DATE_FORMAT(timestamp, string)` is available in the legacy planner but has serious bugs and should not be used.
-Please implement a custom UDF instead or use `EXTRACT` as a workaround.
-{{< /hint >}}
-
-
diff --git a/docs/content/docs/dev/table/modules.md b/docs/content/docs/dev/table/modules.md
index 49a7668..23c0fbb 100644
--- a/docs/content/docs/dev/table/modules.md
+++ b/docs/content/docs/dev/table/modules.md
@@ -83,7 +83,7 @@ Users can use SQL to load/unload/use/list modules in both Table API and SQL CLI.
 {{< tabs "SQL snippets" >}}
 {{< tab "Java" >}}
 ```java
-EnvironmentSettings settings = EnvironmentSettings.newInstance().useBlinkPlanner().build();
+EnvironmentSettings settings = EnvironmentSettings.newInstance().build();
 TableEnvironment tableEnv = TableEnvironment.create(setting);
 
 // Show initially loaded and enabled modules
@@ -168,7 +168,7 @@ tableEnv.executeSql("SHOW FULL MODULES").print();
 {{< /tab >}}
 {{< tab "Scala" >}}
 ```scala
-val settings = EnvironmentSettings.newInstance().useBlinkPlanner().build()
+val settings = EnvironmentSettings.newInstance().build()
 val tableEnv = TableEnvironment.create(setting)
 
 // Show initially loaded and enabled modules
@@ -256,7 +256,7 @@ tableEnv.executeSql("SHOW FULL MODULES").print()
 from pyflink.table import *
 
 # environment configuration
-settings = EnvironmentSettings.new_instance().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().build()
 t_env = TableEnvironment.create(settings)
 
 # Show initially loaded and enabled modules
@@ -456,7 +456,7 @@ Users can use Java, Scala or Python to load/unload/use/list modules programmatic
 {{< tabs "API snippets" >}}
 {{< tab "Java" >}}
 ```java
-EnvironmentSettings settings = EnvironmentSettings.newInstance().useBlinkPlanner().build();
+EnvironmentSettings settings = EnvironmentSettings.newInstance().build();
 TableEnvironment tableEnv = TableEnvironment.create(setting);
 
 // Show initially loaded and enabled modules
@@ -541,7 +541,7 @@ tableEnv.listFullModules();
 {{< /tab >}}
 {{< tab "Scala" >}}
 ```scala
-val settings = EnvironmentSettings.newInstance().useBlinkPlanner().build()
+val settings = EnvironmentSettings.newInstance().build()
 val tableEnv = TableEnvironment.create(setting)
 
 // Show initially loaded and enabled modules
@@ -629,7 +629,7 @@ tableEnv.listFullModules()
 from pyflink.table import *
 
 # environment configuration
-settings = EnvironmentSettings.new_instance().use_blink_planner().build()
+settings = EnvironmentSettings.new_instance().build()
 t_env = TableEnvironment.create(settings)
 
 # Show initially loaded and enabled modules
diff --git a/docs/content/docs/dev/table/sql/explain.md b/docs/content/docs/dev/table/sql/explain.md
index fa71220..4445336 100644
--- a/docs/content/docs/dev/table/sql/explain.md
+++ b/docs/content/docs/dev/table/sql/explain.md
@@ -158,8 +158,6 @@ Flink SQL> EXPLAIN PLAN FOR SELECT `count`, word FROM MyTable1 WHERE word LIKE '
 {{< /tabs >}}
 
 The `EXPLAIN` result is:
-{{< tabs "6ee087b2-3a49-4d75-a803-f436a2166c92" >}}
-{{< tab "Blink Planner" >}}
 ```text
 == Abstract Syntax Tree ==
 LogicalUnion(all=[true])
@@ -179,42 +177,6 @@ Union(all=[true], union all=[count, word])
     TableSourceScan(table=[[default_catalog, default_database, MyTable1]], fields=[count, word])
   TableSourceScan(table=[[default_catalog, default_database, MyTable2]], fields=[count, word])
 ```
-{{< /tab >}}
-{{< tab "Legacy Planner" >}}
-```text
-== Abstract Syntax Tree ==
-LogicalUnion(all=[true])
-  LogicalFilter(condition=[LIKE($1, _UTF-16LE'F%')])
-    FlinkLogicalTableSourceScan(table=[[default_catalog, default_database, MyTable1]], fields=[count, word])
-  FlinkLogicalTableSourceScan(table=[[default_catalog, default_database, MyTable2]], fields=[count, word])
-
-== Optimized Logical Plan ==
-DataStreamUnion(all=[true], union all=[count, word])
-  DataStreamCalc(select=[count, word], where=[LIKE(word, _UTF-16LE'F%')])
-    TableSourceScan(table=[[default_catalog, default_database, MyTable1]], fields=[count, word])
-  TableSourceScan(table=[[default_catalog, default_database, MyTable2]], fields=[count, word])
-
-== Physical Execution Plan ==
-Stage 1 : Data Source
-	content : collect elements with CollectionInputFormat
-
-Stage 2 : Data Source
-	content : collect elements with CollectionInputFormat
-
-	Stage 3 : Operator
-		content : from: (count, word)
-		ship_strategy : REBALANCE
-
-		Stage 4 : Operator
-			content : where: (LIKE(word, _UTF-16LE'F%')), select: (count, word)
-			ship_strategy : FORWARD
-
-			Stage 5 : Operator
-				content : from: (count, word)
-				ship_strategy : REBALANCE
-```
-{{< /tab >}}
-{{< /tabs >}}
 
 {{< top >}}
 
diff --git a/docs/content/docs/dev/table/tableApi.md b/docs/content/docs/dev/table/tableApi.md
index 4ca942b..972363e 100644
--- a/docs/content/docs/dev/table/tableApi.md
+++ b/docs/content/docs/dev/table/tableApi.md
@@ -70,9 +70,8 @@ Table counts = orders
         .groupBy($("a"))
         .select($("a"), $("b").count().as("cnt"));
 
-// conversion to DataSet
-DataSet<Row> result = tEnv.toDataSet(counts, Row.class);
-result.print();
+// print
+counts.execute().print();
 ```
 
 {{< /tab >}}
@@ -104,7 +103,7 @@ val orders = tEnv.from("Orders") // schema (a, b, c, rowtime)
 val result = orders
                .groupBy($"a")
                .select($"a", $"b".count as "cnt")
-               .toDataSet[Row] // conversion to DataSet
+               .execute()
                .print()
 ```
 
@@ -118,7 +117,7 @@ from pyflink.table import *
 
 # environment configuration
 t_env = BatchTableEnvironment.create(
-    environment_settings=EnvironmentSettings.new_instance().in_batch_mode().use_blink_planner().build())
+    environment_settings=EnvironmentSettings.new_instance().in_batch_mode().build())
 
 # register Orders table and Result table sink in table environment
 source_data_path = "/path/to/source/directory/"
@@ -891,8 +890,8 @@ Similar to a SQL JOIN clause. Joins two tables. Both tables must have distinct f
 {{< tabs "innerjoin" >}}
 {{< tab "Java" >}}
 ```java
-Table left = tableEnv.fromDataSet(ds1, "a, b, c");
-Table right = tableEnv.fromDataSet(ds2, "d, e, f");
+Table left = tableEnv.from("MyTable).select($("a"), $("b"), $("c"));
+Table right = tableEnv.from("MyTable).select($("d"), $("e"), $("f"));
 Table result = left.join(right)
     .where($("a").isEqual($("d")))
     .select($("a"), $("b"), $("e"));
@@ -900,8 +899,8 @@ Table result = left.join(right)
 {{< /tab >}}
 {{< tab "Scala" >}}
 ```scala
-val left = ds1.toTable(tableEnv, $"a", $"b", $"c")
-val right = ds2.toTable(tableEnv, $"d", $"e", $"f")
+val left = tableEnv.from("MyTable").select($"a", $"b", $"c")
+val right = tableEnv.from("MyTable").select($"d", $"e", $"f")
 val result = left.join(right).where($"a" === $"d").select($"a", $"b", $"e")
 ```
 {{< /tab >}}
@@ -929,8 +928,8 @@ Both tables must have distinct field names and at least one equality join predic
 {{< tabs "outerjoin" >}}
 {{< tab "Java" >}}
 ```java
-Table left = tableEnv.fromDataSet(ds1, "a, b, c");
-Table right = tableEnv.fromDataSet(ds2, "d, e, f");
+Table left = tableEnv.from("MyTable).select($("a"), $("b"), $("c"));
+Table right = tableEnv.from("MyTable).select($("d"), $("e"), $("f"));
 
 Table leftOuterResult = left.leftOuterJoin(right, $("a").isEqual($("d")))
                             .select($("a"), $("b"), $("e"));
@@ -942,8 +941,8 @@ Table fullOuterResult = left.fullOuterJoin(right, $("a").isEqual($("d")))
 {{< /tab >}}
 {{< tab "Scala" >}}
 ```scala
-val left = tableEnv.fromDataSet(ds1, $"a", $"b", $"c")
-val right = tableEnv.fromDataSet(ds2, $"d", $"e", $"f")
+val left = tableEnv.from("MyTable").select($"a", $"b", $"c")
+val right = tableEnv.from("MyTable").select($"d", $"e", $"f")
 
 val leftOuterResult = left.leftOuterJoin(right, $"a" === $"d").select($"a", $"b", $"e")
 val rightOuterResult = left.rightOuterJoin(right, $"a" === $"d").select($"a", $"b", $"e")
@@ -977,8 +976,8 @@ An interval join requires at least one equi-join predicate and a join condition
 {{< tabs "intervaljoin" >}}
 {{< tab "Java" >}}
 ```java
-Table left = tableEnv.fromDataSet(ds1, $("a"), $("b"), $("c"), $("ltime").rowtime());
-Table right = tableEnv.fromDataSet(ds2, $("d"), $("e"), $("f"), $("rtime").rowtime()));
+Table left = tableEnv.from("MyTable).select($("a"), $("b"), $("c"), $("ltime"));
+Table right = tableEnv.from("MyTable).select($("d"), $("e"), $("f"), $("rtime"));
 
 Table result = left.join(right)
   .where(
@@ -992,8 +991,8 @@ Table result = left.join(right)
 {{< /tab >}}
 {{< tab "Scala" >}}
 ```scala
-val left = ds1.toTable(tableEnv, $"a", $"b", $"c", $"ltime".rowtime)
-val right = ds2.toTable(tableEnv, $"d", $"e", $"f", $"rtime".rowtime)
+val left = tableEnv.from("MyTable").select($"a", $"b", $"c", $"ltime")
+val right = tableEnv.from("MyTable").select($"d", $"e", $"f", $"rtime")
 
 val result = left.join(right)
   .where($"a" === $"d" && $"ltime" >= $"rtime" - 5.minutes && $"ltime" < $"rtime" + 10.minutes)
@@ -1587,7 +1586,7 @@ table = input.window([w: GroupWindow].alias("w")) \
 {{< /tab >}}
 {{< /tabs >}}
 
-The `Window` parameter defines how rows are mapped to windows. `Window` is not an interface that users can implement. Instead, the Table API provides a set of predefined `Window` classes with specific semantics, which are translated into underlying `DataStream` or `DataSet` operations. The supported window definitions are listed below.
+The `Window` parameter defines how rows are mapped to windows. `Window` is not an interface that users can implement. Instead, the Table API provides a set of predefined `Window` classes with specific semantics. The supported window definitions are listed below.
 
 #### Tumble (Tumbling Windows)