[
https://issues.apache.org/jira/browse/FLINK-25435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465670#comment-17465670
]
Moses edited comment on FLINK-25435 at 12/27/21, 10:24 AM:
-----------------------------------------------------------
[~nicholasjiang] , the main reason is that SET statement will not alter CLI
timely, and that's why I wanna do so. The CLI will be determined when SQL
Client starts.
was (Author: zhangchaoming):
[~nicholasjiang] , the main reason is that SET statement will not alter CLI
timely, and that's why I wanna do so.
> 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)
