You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/07/10 07:47:00 UTC
[jira] [Created] (FLINK-18556) Drop the unused options in
TableConfig
Jark Wu created FLINK-18556:
-------------------------------
Summary: Drop the unused options in TableConfig
Key: FLINK-18556
URL: https://issues.apache.org/jira/browse/FLINK-18556
Project: Flink
Issue Type: Sub-task
Components: Table SQL / API
Reporter: Jark Wu
As disucssed in FLINK-16835, the following {{TableConfig}} options are not preserved:
* {{nullCheck}}: Flink will automatically enable null checks based on the table schema ({{NOT NULL}} property)
* {{decimalContext}}: this configuration is only used by the legacy planner which will be removed in one of the next releases
* {{maxIdleStateRetention}}: is automatically derived as 1.5* {{idleStateRetention}} until StateTtlConfig is fully supported (at which point only a single parameter is required).
The blink planner should remove the dependencies on {{nullCheck}} and {{maxIdleStateRetention}} first. Besides, this maybe blocked by when to drop old planner, because old planner is still using them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)