Github user tgravescs commented on the issue:

    https://github.com/apache/spark/pull/18070
  
    sorry for my delay on getting back to this.
    So if we do that you would have to have taskKilledReason extend 
TaskFailedReason so because things rely on the countTowardsTaskFailures field. 
Then we would want to go through everywhere those are used and see if we need 
to update the other code. It doesn't look like there would be to many places to 
update so I think this approach sounds good.  If you find something that its 
painful to update then just updating JobProgressListener in a few place would 
be fine also.
    



---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to