[
https://issues.apache.org/jira/browse/SPARK-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410596#comment-15410596
]
Jan Gorecki commented on SPARK-16864:
-------------------------------------
Record exact spark source code reference while processing ETL workflow so
performance implication can be measures precisely referencing point in time of
source code. I doubt if version number or date/time is a natural key for spark
source code, is it? If you don't have a natural key you can't build reliable
workflow. How would you automatically git clone, reset, build, deploy and
re-run your workflow - based on data collected by spark - if you don't even
have git commit there? Lookup git commit hash by version and date... sure it
works, but why users can't just access that info directly? I don't see ANY
reason to not have that feature? If you have any I would be glad to read. And
no, even for developers that info is not available on runtime.
> 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
