Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/21546
Yes, that is the worst case. If there is some bug with types/schema then
there is an automatic fallback to the non-arrow code path too
On Tue, Aug 28, 2018, 7:16 PM Xiao Li <notificati...@github.com> wrote:
> @BryanCutler <https://github.com/BryanCutler> The worst case is to turn
> off spark.sql.execution.arrow.enabled, if the new code path has a bug,
> right?
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/21546#issuecomment-416800476>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AEUwdeFLnFzURZmVk4wwwcJJhBumZJeqks5uVfligaJpZM4UlMKq>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
