Github user markhamstra commented on the pull request:

    https://github.com/apache/spark/pull/186#issuecomment-38650754
  
    I look at it differently, Patrick.  Our current handling of exceptions 
thrown within the DAGScheduler is already completely broken -- luckily, they're 
fairly rare.  If we screw up the attempt to handle them better, we don't end up 
any more completely broken.  If we get it at least partially right, we're in 
better shape. 


---
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.
---

Reply via email to