[
https://issues.apache.org/jira/browse/FLINK-36620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonard Xu reassigned FLINK-36620:
----------------------------------
Assignee: zjjiang
> Add support for the flink-home parameter to be set in both “--flink-home
> $FLINK_HOME” and “--flink-home=$FLINK_HOME” formats
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-36620
> URL: https://issues.apache.org/jira/browse/FLINK-36620
> Project: Flink
> Issue Type: Improvement
> Components: Flink CDC
> Affects Versions: cdc-3.1.0, cdc-3.2.0, cdc-3.1.1
> Reporter: zjjiang
> Assignee: zjjiang
> Priority: Major
> Labels: pull-request-available
> Fix For: cdc-3.3.0
>
>
> Currently, most of FlinkCDC's command line arguments are supported in the
> format `\-\-$KEY $VALUE` or `\-\-$KEY=$VALUE`, e.g. --jar, but, except for
> flink home, which only supports space spacing. Users who use the
> `\-\-flink-home=$FLINK_HOME` format on the command line (trying to be
> consistent with the other = spacing arguments) will not be able to set flink
> home correctly.
> In particular, when there is an environment variable $FLINK_HOME and you want
> to override it by setting --flink-home=/path/to/new/flink/home, you will find
> that it does not work.
> We would like to support the flink-home parameter in both --flink-home
> $FLINK_HOME and --flink-home=$FLINK_HOME formats, so that users can avoid
> formatting differences and runtime exceptions when using command line
> arguments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
