[
https://issues.apache.org/jira/browse/FLINK-18556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17327744#comment-17327744
]
Flink Jira Bot commented on FLINK-18556:
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> 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
>Priority: Major
> Labels: stale-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.3.4#803005)
