[
https://issues.apache.org/jira/browse/FLINK-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061695#comment-17061695
]
Timo Walther commented on FLINK-13691:
--------------------------------------
We can remove this deprecated method now. Actually, I started with it but I
stopped because we were missing a validation feature in ConfigOptions that
ensures that min and max retention time satisfies some conditions (e.g. min is
always smaller than max and some minimum difference).
We can solve this by having a little config option validation utility at a
well-defined location close to the config option. The min/max value should only
be used after calling this utility.
> Remove deprecated query config
> ------------------------------
>
> Key: FLINK-13691
> URL: https://issues.apache.org/jira/browse/FLINK-13691
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Assignee: jinhai
> Priority: Major
>
> In Flink 1.9 the query config was marked deprecated and integrated into
> TableConfig. We should remove it from the API to reduce complexity and
> confusion.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
