[
https://issues.apache.org/jira/browse/SPARK-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410856#comment-15410856
]
Sean Owen commented on SPARK-16864:
-----------------------------------
Yeah you've hit it on the head: git hash is really only relevant for source
code and some kind of build workflow. Within released software at runtime, the
only meaningful version indicator is the version x.y.z or maybe a snapshot
timestamp, because they're ordered and you might reason about them in code. The
only thing you can do with a hash is log it. You already have the git hash in
your workflow and can use it, because you are specifically interested in
building from hashes and noting it. You haven't provided a use case for writing
an app that depends on a hash - it works that way, not "give me any reason not
to have this".
> Comprehensive version info
> ---------------------------
>
> Key: SPARK-16864
> URL: https://issues.apache.org/jira/browse/SPARK-16864
> Project: Spark
> Issue Type: Improvement
> Reporter: jay vyas
>
> Spark versions can be grepped out of the Spark banner that comes up on
> startup, but otherwise, there is no programmatic/reliable way to get version
> information.
> Also there is no git commit id, etc. So precise version checking isnt
> possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
