flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vinoyang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10771) Replace hard code of job graph file path with config option for FileJobGraphRetriever
Date Mon, 05 Nov 2018 11:39:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675004#comment-16675004
] 

vinoyang commented on FLINK-10771:
----------------------------------

[~till.rohrmann] What do you think of this issue? At present, internal.jobgraph-path does
not seem to be developed for user configuration. But if we only use the default value, it
seems that there is no need to have this ConfigOption.

> Replace hard code of job graph file path with config option for FileJobGraphRetriever
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-10771
>                 URL: https://issues.apache.org/jira/browse/FLINK-10771
>             Project: Flink
>          Issue Type: Improvement
>          Components: YARN
>            Reporter: vinoyang
>            Assignee: vinoyang
>            Priority: Major
>
> There is a config option to configure the value :
> {code:java}
> public static final ConfigOption<String> JOB_GRAPH_FILE_PATH = ConfigOptions
>    .key("internal.jobgraph-path")
>    .defaultValue("job.graph");
> {code}
> However, we used the default hard code in AbstractYarnClusterDescriptor. 
> This is just a preliminary refactoring, and I finally recommend that we use Zookeeper-based
storage. It has been implemented in FLINK-10292.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message