Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/12152#issuecomment-207461399
Sorry if that wasn't clear, the motivation is to more easily tie this to
automated continuous integration and deployment and to easily have
traceability.
Part of this is right now you have to manually change a java file to change
the version that comes out when you run spark-submit --version. With
continuous integration the build numbers could be something like 1.6.1.X (where
X increments on each change) and I want to see the exact version easily.
Having to manually change a java file makes that hard. obviously that should
make the apache spark releases easier as you don't have to manually change this
file as well.
The other important part for me is the git information. This easily lets
me trace it back to exact commits. We have a multi-tenant YARN cluster and
users can run many different versions at once. I want to be able to see
exactly which version they are running. The reason to know exact version can
range from helping debug some problem to making sure someone didn't hack
something in Spark to cause bad things (generally they should use approved
version), etc.
---
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]
