Github user JoshRosen commented on the pull request: https://github.com/apache/spark/pull/2824#issuecomment-59468593 Maybe this is being overly-conservative, but could we add an undocumented configuration option that allows users to bypass the `transferTo` here? If we ship 1.1.1 or 1.2 and this bug resurfaces, it would be nice if there was a way for users to revert back to the older version of this code without having to recompile. A lot of users can't simply upgrade their kernel, so I think we need to offer an easy workaround for them.
--- 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