Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38651340
I actually don't think this change will be that invasive, and it fixes an
annoying issue (that is a regression in 0.9) so I think it should go into
the 0.9 branch, but given timing I don't think 0.9.1 makes sense (since
there isn't even a patch for this yet!).
On Tue, Mar 25, 2014 at 10:16 PM, Mark Hamstra
<[email protected]>wrote:
> 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.
>
> --
> Reply to this email directly or view it on
GitHub<https://github.com/apache/spark/pull/186#issuecomment-38650754>
> .
>
---
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.
---
