You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:23:16 UTC
[jira] [Updated] (SPARK-10950) ApplicationHistoryInfo to include
spark version; History Server to report incompatibility with later versions
[ https://issues.apache.org/jira/browse/SPARK-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-10950:
---------------------------------
Labels: bulk-closed (was: )
> ApplicationHistoryInfo to include spark version; History Server to report incompatibility with later versions
> -------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-10950
> URL: https://issues.apache.org/jira/browse/SPARK-10950
> Project: Spark
> Issue Type: Improvement
> Components: Web UI
> Affects Versions: 1.5.1
> Reporter: Steve Loughran
> Priority: Minor
> Labels: bulk-closed
>
> The history server cannot provide guarantees of forward compatibility -it's unrealistic. What happens today is that the user gets to see a stack trace, perhaps when attempting to unmarshall a JSON-formatted event which isn't known about.
> If {{ApplicationHistoryInfo}} included a version field, and history providers included and later retrieved version information in their histories, then the UI could recognise incompatible histories and present them differently. In the main UI, somehow indicating that they weren't readable; perhaps with the URL being bonded to a page saying "incompatible version".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org