Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7732#issuecomment-126878276
I might slightly prefer to just allow users to specify files with something
like `--conf X --conf Y` and then those files are put in the conf directory of
the distribution. The issue with the proposed approach is (a) it sort of
changes the nature of make-distribution, which to this point has assumed
everything is computable from an unmodified spark source tree (b) it's a
breaking change from earlier versions so could have minor unexpected annoyances
for people.
In terms of having this feature at all vs not having it in the first place.
It seems like the best user workaround without having this in the script is to
just add a conf post-hoc, which could involve untarring and re-tarring, which
is pretty cumbersome. So I do think it's good to come up with some solution
that makes this easy for packagers to add a conf.
---
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]
