Github user corruptmemory commented on the pull request:
https://github.com/apache/spark/pull/13279#issuecomment-221903782
Understood that this fix is upstream -- that's where I got the patch that
started this.
This fix is (according to the original PR) something that made something
work that was supposed to work but didn't. Assuming that the patch I started
with was focused on addressing only fixing the non-functional shuffle service
then this current PR should inherit that property. I haven't knowingly
extended the scope of the intended fix. At the moment my user is not going to
be deploying 2.0 anytime soon (they are still in the process of rolling out
1.6) so there is some value in knowing that any further attention to fixing
bugs for 1.6 takes into account fixes in the context of a working shuffle
service.
---
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]
