[
https://issues.apache.org/jira/browse/SPARK-26417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcelo Vanzin resolved SPARK-26417.
------------------------------------
Resolution: Won't Fix
If you're talking about the constants in {{SparkAppHandle.State}}, the names
are mostly self-describing, the comments are there to make the javadoc nicer.
I don't see a point in exposing the content of the comments to code.
> Make comments for states available for logging
> ----------------------------------------------
>
> Key: SPARK-26417
> URL: https://issues.apache.org/jira/browse/SPARK-26417
> Project: Spark
> Issue Type: Wish
> Components: Java API, Spark Core
> Affects Versions: 2.3.2, 2.4.0
> Reporter: Evgenii Lartcev
> Priority: Minor
>
> When add an extra `SparkListener`, it would be very useful (in productionÂ
> applications) to get the description of a state. For now it only available as
> comments in code. As suggestion it could be moved into constructor as well as
> finalization flag at enum org.apache.spark.launcher.SparkAppHandle.State
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
