I think the code that submits the job can create an archive of all the files in
the “resources”, this making sure that they stay together. This file would then
be placed in the distributed cache. When executing the contents of the archive
can be extracted again and be used, since they still maintain the same relative
folder structure. What do you think?
> On 15. Jun 2017, at 13:53, yunfan123 <yunfanfight...@foxmail.com> wrote:
>
> Yes.
> My resource file is python or other script reference to each other by
> relative path.
> What I want is all my resource file in one job place in one directory.
> And the resource files in different jobs can't place in one directory.
> The distributedCache can not guarantee this.
>
>
>
> --
> View this message in context:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/User-self-resource-file-tp13693p13762.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at
> Nabble.com.
