Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14275#discussion_r71868244
--- Diff: core/src/main/scala/org/apache/spark/TaskState.scala ---
@@ -49,5 +49,6 @@ private[spark] object TaskState extends Enumeration {
case MesosTaskState.TASK_KILLED => KILLED
case MesosTaskState.TASK_LOST => LOST
case MesosTaskState.TASK_ERROR => LOST
+ case MesosTaskState.TASK_KILLING => RUNNING
--- End diff --
Is it maybe clearer to use `case x | y | z => foo` syntax here to show
clearly which several cases map to one output state? here and above. Either
that, or at least loosely group the inputs; KILLING seems like it should be
next to KILLED
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
