Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/2422#issuecomment-56373277
Is there an example of how this is going to be leveraged ?
The default case is the simple version delegating to existing spark - would
be good to see how this is used against tez - so that there is a clearer
picture of how the design changes fit into overall changes proposed : and what
further changes (if any) might be required in case we need to generalize the
interface.
As @pwendell mentioned, currently this aspect is not exposed - and if we
want to expose it via an spi, we need to have better understanding of how it
will be leveraged.
Also, would Experimental make more sense than DeveloperApi (until it
stabilizes) ?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
