Is there a way to pass configuration file resources to be resolvable through the classloader?
For example, if I'm using a library (non-spark) that can use a some-lib.properties file in the classpath/classLoader, can I pass that file so that when it tries to get the resource from the classloader it is able to find it? One potential solution is to take the files and package them as resources in a jar, and include the jar as part of the spark job, but that feels like a hack instead of an actual solution. Is there any support or planned support for such a thing? https://github.com/apache/spark/pull/9118 seems to tackle a similar problem in a hard-coded kind of way. Thank you, Charles Allen
