Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/791#issuecomment-62332299
This has mostly gone stale so I'd suggest we close this issue and revisit
this later. This is a decent idea, but it does complicate things a good amount,
and this particular piece of code IMO is already quite complicated. As with any
performance change, it would be useful to quantify the performance problems
observed as a result of this issue. For instance, has it been observed as a
bottleneck in real clusters? Putting information of this type on the JIRA would
be useful.
---
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
