[jira] [Updated] (SPARK-26417) Make comments for states available for logging
[ https://issues.apache.org/jira/browse/SPARK-26417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Lartcev updated SPARK-26417: Description: 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 (was: When add an extra `SparkListener`, it would be very useful (in production applications) to get the description of a state. 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) > 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
[jira] [Updated] (SPARK-26417) Make comments for states available for logging
[ https://issues.apache.org/jira/browse/SPARK-26417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Lartcev updated SPARK-26417: Description: When add an extra `SparkListener`, it would be very useful (in production applications) to get the description of a state. 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 (was: When add an extra `SparkListener`, it would be very useful (in production applications) to get the description of a state. Now it only available in comments. As suggestion it could be moved into constructor as well as finalization flag at enum org.apache.spark.launcher.SparkAppHandle.State) > 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. 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
[jira] [Updated] (SPARK-26417) Make comments for states available for logging
[ https://issues.apache.org/jira/browse/SPARK-26417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Lartcev updated SPARK-26417: Description: When add an extra `SparkListener`, it would be very useful (in production applications) to get the description of a state. Now it only available in comments. As suggestion it could be moved into constructor as well as finalization flag at enum org.apache.spark.launcher.SparkAppHandle.State (was: When add an extra `SparkListener`, it would be very useful in production mode to get the description of a state. Now it only available in comments. As suggestion it could be moved into constructor as well as finalization flag at enum org.apache.spark.launcher.SparkAppHandle.State) > 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. Now it only available in > comments. 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
[jira] [Updated] (SPARK-26417) Make comments for states available for logging
[ https://issues.apache.org/jira/browse/SPARK-26417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Lartcev updated SPARK-26417: Affects Version/s: 2.3.2 > 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 mode > to get the description of a state. Now it only available in comments. 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
[jira] [Updated] (SPARK-26417) Make comments for states available for logging
[ https://issues.apache.org/jira/browse/SPARK-26417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Lartcev updated SPARK-26417: Description: When add an extra `SparkListener`, it would be very useful in production mode to get the description of a state. Now it only available in comments. As suggestion it could be moved into constructor as well as finalization flag at enum org.apache.spark.launcher.SparkAppHandle.State (was: When add an extra `SparkListener`, it would be very useful in production mode to get the description of a state. Now it only available in comments. As suggestion it could be moved into constructor as well as finalization flag.) > 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 mode > to get the description of a state. Now it only available in comments. 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
