[
https://issues.apache.org/jira/browse/FLINK-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-5516.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Separate config options for all paths were introduced in
bdcebfda06846a1e21bb6a4678909d503ebc6333.
`python.plan.tmp.dir` - configures the path on the client where temporary files
are stored
`python.mmap.tmp.dir` - configures the path where the memory-mapped files are
stored on the TaskManagers
`python.dc.tmp.dir` - configures the path where the python library, plan file
and additional files will be uploaded to before registering them with the DC
> Hardcoded paths in flink-python/.../PythonPlanBinder.java
> ---------------------------------------------------------
>
> Key: FLINK-5516
> URL: https://issues.apache.org/jira/browse/FLINK-5516
> Project: Flink
> Issue Type: Improvement
> Components: Python API
> Reporter: Felix seibert
> Assignee: Chesnay Schepler
> Fix For: 1.3.0
>
>
> The PythonPlanBinder.java contains three hardcoded filesystem paths:
> {code:java}
> public static final String FLINK_PYTHON_FILE_PATH =
> System.getProperty("java.io.tmpdir") + File.separator + "flink_plan";
> private static String FLINK_HDFS_PATH = "hdfs:/tmp";
> public static final String FLINK_TMP_DATA_DIR =
> System.getProperty("java.io.tmpdir") + File.separator + "flink_data";
> {code}
> _FLINK_PYTHON_FILE_PATH_ and _FLINK_TMP_DATA_DIR_ are configurable by
> modifying _java.io.tmpdir_.
> For _FLINK_HDFS_PATH_, there is no way of configuring otherwise but modifying
> the source.
> Is it possible to make all three parameters configurable in the usual flink
> configuration files (like flink-conf.yaml)?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
