Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6291#issuecomment-154514338
sorry for the delayed review @markhamstra. just some minor comments,
otherwise lgtm.
As far as the sql executionId, I assume this change is also the right fix
there as well -- it would be pretty weird if the executionId was supposed to
retain the old value, even after the original job had been cancelled? Or are
you just saying this fix is more important than we thought? Of course, the
executionId suffers from the same problem we've already noted with properties &
priority, that a taskSet which was already started is still "stuck" with the
executionId it started with.
---
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]
