[
https://issues.apache.org/jira/browse/FLINK-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-13127.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.10.0
Release Note: This change orders the shipped files wrt to resources and
jar files as well as alphabetically in these groups.
Fixed via 17e2747e575cc4d9847be76b5ce9a75a7b6707f7
> "--yarnship" doesn't support resource classloading
> --------------------------------------------------
>
> Key: FLINK-13127
> URL: https://issues.apache.org/jira/browse/FLINK-13127
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.8.1
> Reporter: David Moravek
> Assignee: David Moravek
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently yarnship works as follows:
> * user specifies directory to ship with the job
> * yarn ships it with the container
> * org.apache.flink.yarn.AbstractYarnClusterDescriptor#uploadAndRegisterFiles
> traverses directory recursively and adds each file to the classpath
> This works well for shipping jars, but doesn't work correctly with shipping
> resources that we want to load using java.lang.ClassLoader#getResource method.
> In order to make resource classloading work, we need to register it's
> directory instead of the file itself (java classpath expects directories or
> archives).
> CLASSPATH="shipped/custom.conf:${CLASSPATH}" needs to become
> CLASSPATH="shipped:${CLASSPATH}"
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
