xuechendi commented on a change in pull request #34396:
URL: https://github.com/apache/spark/pull/34396#discussion_r747265107



##########
File path: sql/core/src/main/scala/org/apache/spark/sql/execution/Columnar.scala
##########
@@ -458,6 +462,34 @@ case class RowToColumnarExec(child: SparkPlan) extends 
RowToColumnarTransition {
     // This avoids calling `schema` in the RDD closure, so that we don't need 
to include the entire
     // plan (this) in the closure.
     val localSchema = this.schema
+    if (enableArrowColumnVector) {
+      val maxRecordsPerBatch = SQLConf.get.arrowMaxRecordsPerBatch
+      val timeZoneId = SQLConf.get.sessionLocalTimeZone
+      return child.execute().mapPartitionsInternal { rowIterator =>
+        val context = TaskContext.get()
+        val allocator = ArrowUtils.getDefaultAllocator
+        val bytesIterator = ArrowConverters
+          .toBatchIterator(rowIterator, localSchema, maxRecordsPerBatch, 
timeZoneId, context)

Review comment:
       @HyukjinKwon , `ArrowToColumnarExec`  is not needed because 
`ArrowColumnVector` is derived from `ColumnVector`, so current 
`ColumnarToRowExec` is capable of converting Arrow ColumnarBatch to 
InternalRow. 
   And for `ColumnarToArrowExec`, there is some built-in rules [codes 
link](https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/Columnar.scala#L512-L558)
 will add a  `ColumnarToRowExec` between two SparkPlans, if we use a new 
SparkPlan then we need to change above codes as well. So I am hoping we don't 
add these two new physical plans.
   For mapInArrow case, how about we add a new parameter in RowToColumnarExec 
to tell it to use Arrow.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to