[
https://issues.apache.org/jira/browse/FLINK-25435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464936#comment-17464936
]
Nicholas Jiang commented on FLINK-25435:
----------------------------------------
[~ZhangChaoming], even though the description of
`$internal.deployment.config-dir` indicates that *DO NOT USE*, we should not
set this configuration in `DefaultCLI` for the SET statement. We could
determine the CLI by check this configuration.
> Can not read jobmanager/taskmanager.log in yarn-per-job mode.
> -------------------------------------------------------------
>
> Key: FLINK-25435
> URL: https://issues.apache.org/jira/browse/FLINK-25435
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Client
> Affects Versions: 1.14.0
> Reporter: Moses
> Priority: Major
>
> I'm using SQL Client to submit a job, and using `SET` statement to specify
> deploy mode.
> {code:sql}
> SET execution.target=yarn-per-job;
> ...
> {code}
> But I can not found log files both on master and taskmanagers.
> I found that `GenericCLI` and `FlinkYarnSessionCli` will set
> `$internal.deployment.config-dir={configurationDirectory}` in their execution
> configuration.
> Should we set this configuration in `DefaultCLI` as well?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
