Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5403#issuecomment-96267909
My understanding was this wouldn't be an "experimental" feature in terms of
how we've defined that in the past (i.e. it's not on a path to being something
we'd expect people to ever use in production). It would just be an internal
flag we could set when doing measurement work. We've never had such a feature
before in the code base, so it's a bit of a question about whether we want to
do that in general.
I'm neutral to slightly positive on that idea. I think we'd just have it be
undocumented and print a large warning that it's only for benchmarking work. I
don't think this would add much more burden if the shuffle interface changes
because it is ultimately much simpler than either of the existing two shuffles.
I don't think this can possibly exist outside of the codebase because it uses
the block storage API's.
On the other hand, I can see this percolating around on mailing lists, etc
as a way to "speed up your spark job". So there is an element of wanting to
protect users from themselves and not have this in the codebase in a way that's
easily accessible.
---
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]
