Github user StephanEwen commented on the pull request: https://github.com/apache/flink/pull/593#issuecomment-95868495 I think that keeping the classpaths in sync is really crucial. What is the problem in exposing this to the client as well? Can we make the following assumptions for the use case where we need the global class path: - The URL is either a file path that points to a directory accessible to all nodes (NFS or so) and the client runs in the cluster as well. - The URL is an HTTP URL or so that points to a file server that serves the classes to work in non-shared directory settings. Some other remark: This makes the code quite dirty on a lot of parts, since we have always Files and URLs in Client, executors, ... Can we not store everything as URLs (rather than having Strings for jar files and URLs extra). Files can be expressed as URLs anyways as well...
--- 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. ---