Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4683#issuecomment-75108475
@zhzhan I think you're missing my point. I don't want to share my patch
because it uses internal Yarn APIs. We don't want to include such code in Spark
because it's bad practice to do so.
Your code uses the same internal APIs. Until you fix that, your patch will
also not go forward, just as mine wouldn't.
It's not about me not wanting your patch to go in because I have a similar
one. It's because your patch, like mine, has a fatal flaw that makes it not
suitable for inclusion in Spark. Fix that flaw and we can go ahead.
---
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]
