spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Gorecki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-16864) Comprehensive version info
Date Fri, 05 Aug 2016 22:51:20 GMT

    [ https://issues.apache.org/jira/browse/SPARK-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410238#comment-15410238
] 

Jan Gorecki commented on SPARK-16864:
-------------------------------------

Hi, git commit is relevant to applications at runtime as long as the subject for an application
(in any dimension) is spark itself. I don't understand why that info would not be included.
This may not be a problem for people who build from source, they can eventually put that metadata
in plaintext file (still an overhead). The bigger problem is for those who just grab binaries
and for example just want to track performance in their cluster over spark git history. Git
commit hash is a natural key for a source code a project, you won't find better field to references
the source code. Referencing release versions is simply a different thing.

> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message