Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/1090#issuecomment-137477152
Thanks for your pull request! I'm assuming you would use this utility to
copy files from your local to a remote file system, right? Your utility starts
a Flink job to copy the files to the remote file systems. This only works if
you execute it locally because otherwise the task managers need to have the
files available and that might defeat the utility's purpose. Also, imagine
someone embedding the tool in a Flink program. The person might wonder why
his/her program actually executes two jobs (one for the utility, one for the
actual job).
I think this would be more useful as a utility function, e.g. in a
`FileUtils` class in `flink-core`. The method there would receive a list of
files and then upload the files like you did using Flink's `FileSystem`
abstraction. We could still parallelize the method by starting multiple threads
to upload the files.
Correct me if I'm wrong or misunderstood your pull request :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
