Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/6291#issuecomment-154521405
@squito Yes, I'm pretty sure that this is the right fix for executionId as
well. I'm just saying that previously we were talking about losing the job's
properties only really affecting scheduling priority and job description, so
there wasn't much impact to using the prior safe-but-not-quite-correct fix.
With Spark SQL also relying upon the job properties, it's a little more
important to make sure they are correct.
---
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]
