Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/5085#issuecomment-83891733
Marcelo, consider the following use case and see if it makes sense: I'm a
savvy customer. I name my jar file "spark-assembly.jar" because I see that as
the outermost jar file in CDH (I get rid of unnecessary symlinks). I modify (or
rather bypass) most of compute-classpath.sh including the check for jar file
name. Now I find that the check for the jar file name (which was a bad idea to
begin with) is part of Spark code that gets compiled and therefore cannot be
easily modified.
Btw, is having strict checks on assembly jar names a good idea? Or should I
be able to name my jar "assembly.jar" as long as it is the only one and in the
right folder?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
