You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Weijie Guo (Jira)" <ji...@apache.org> on 2024/07/10 06:58:09 UTC
[jira] [Updated] (FLINK-17535) Treat min/max as part of the hierarchy of config option
[ https://issues.apache.org/jira/browse/FLINK-17535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weijie Guo updated FLINK-17535:
-------------------------------
Fix Version/s: 2.0.0
(was: 1.20.0)
> Treat min/max as part of the hierarchy of config option
> -------------------------------------------------------
>
> Key: FLINK-17535
> URL: https://issues.apache.org/jira/browse/FLINK-17535
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Yangze Guo
> Priority: Minor
> Labels: auto-deprioritized-major
> Fix For: 2.0.0
>
>
> As discussed in http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Should-max-min-be-part-of-the-hierarchy-of-config-option-td40578.html. We decide to treat min/max as part of the hierarchy of config option. This ticket is an umbrella of all tasks related to it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)