You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/07/06 22:39:00 UTC
[jira] [Updated] (FLINK-22257) Clarify Flink ConfigOptions Usage
[ https://issues.apache.org/jira/browse/FLINK-22257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-22257:
-----------------------------------
Labels: auto-deprioritized-major stale-minor usability (was: auto-deprioritized-major usability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Clarify Flink ConfigOptions Usage
> ---------------------------------
>
> Key: FLINK-22257
> URL: https://issues.apache.org/jira/browse/FLINK-22257
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Fabian Paul
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, usability
>
> For users, it is hard to determine which ConfigOptions are relevant for the different stages of a Flink application.
> Beginning from the translation of the user program to the execution on the cluster. In particular which options can be configured through the different channels.
> * Cluster configuration (i.e. flink-conf.yaml)
> * Application configuration, code-based
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)