Github user JustinPihony commented on the issue:
https://github.com/apache/spark/pull/14077
Then the best course of action would be to use my current impl as it works
no matter the position of copy. I can add the additional tests if that would
make it more amenable? Otherwise I'll push a reduced code set in the morning,
but it would rely on the copy location move PR
> On Jul 7, 2016, at 1:27 AM, Hyukjin Kwon <[email protected]> wrote:
>
> (Personally, I hope this does not get delayed because this usage was
introduced in Spark Summit PPT and I guess users would try to use this API.)
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
---
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]
