Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/4957#issuecomment-95175963
I suggest not making invasive changes as part of this JIRA. This is flaky
test fix jira, and changing the performance-critical flow of data is a bad
idea.
On Wed, Apr 22, 2015 at 3:51 AM, Kevin <[email protected]> wrote:
> I think we will still have a problem with upper bounding the blocks if we
> just use timers, that was the original issue. I agree with the point on
> performance though. I'll have another look and see if I can combine the
two
> approaches to get rid of the copy somehow.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/4957#issuecomment-95133444>.
>
---
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]
