[
https://issues.apache.org/jira/browse/FLINK-17535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17535:
-----------------------------------
Labels: auto-deprioritized-major (was: stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> 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.14.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.3.4#803005)
