You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Marios Trivyzas (Jira)" <ji...@apache.org> on 2022/04/08 08:52:00 UTC

[jira] [Assigned] (FLINK-18556) Drop the unused options in TableConfig

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

Marios Trivyzas reassigned FLINK-18556:
---------------------------------------

    Assignee: Marios Trivyzas

> 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
>            Assignee: Marios Trivyzas
>            Priority: Major
>
> 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.20.1#820001)