[
https://issues.apache.org/jira/browse/FLINK-21126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810859#comment-17810859
]
Junrui Li commented on FLINK-21126:
-----------------------------------
After reviewing the considerations for deprecating the FLINK_PROPERTIES
environment variable in Docker scripts for Flink 2.0, we have decided to retain
this feature for the time being.
The upcoming code freeze for Flink-1.19 on January 25, 2024, does not leave us
with sufficient time to undergo the required community discussions and voting
process, considering that FLINK_PROPERTIES is part of the public API.
Moreover, removing support for FLINK_PROPERTIES would not significantly ease
the user experience or reduce code complexity. In fact, it could introduce
unnecessary migration costs for our users.
Given these points, we plan not to include this change in the scope of
Flink-2.0.
> Reconsider FLINK_PROPERTIES
> ---------------------------
>
> Key: FLINK-21126
> URL: https://issues.apache.org/jira/browse/FLINK-21126
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Scripts
> Reporter: Chesnay Schepler
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
> Fix For: 2.0.0
>
>
> The docker scripts support a {{FLINK_PROPERTIES}} environment variable that
> contains a multi-line string with config options, that is piped into the
> configuration.
> This variable is somewhat redundant, because docker users can also specify a
> list of dynamic properties when starting a container, and Kubernetes users
> are advised to use config maps instead.
> FLIP-161 might also re-introduce new ways to configure Flink via environment
> variables.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
