You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:07 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 ]

Yun Gao updated FLINK-17535:
----------------------------
    Fix Version/s: 1.16.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: 1.15.0, 1.16.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.1#820001)