Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/20678#discussion_r171139748
--- Diff: docs/sql-programming-guide.md ---
@@ -1689,6 +1689,10 @@ using the call `toPandas()` and when creating a
Spark DataFrame from a Pandas Da
`createDataFrame(pandas_df)`. To use Arrow when executing these calls,
users need to first set
the Spark configuration 'spark.sql.execution.arrow.enabled' to 'true'.
This is disabled by default.
+In addition, optimizations enabled by 'spark.sql.execution.arrow.enabled'
will fallback automatically
+to non-optimized implementations if an error occurs. This can be
controlled by
--- End diff --
Let me try to rephrase this doc a bit. The point I was trying to make in
this fallback (for now) was, to only do the fallback before the actual
distributed computation within Spark.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
