sven-weber-db commented on code in PR #55768: URL: https://github.com/apache/spark/pull/55768#discussion_r3233685181
########## sql/core/src/main/scala/org/apache/spark/sql/execution/externalUDF/ExternalUDFExec.scala: ########## @@ -0,0 +1,83 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.spark.sql.execution.externalUDF + +import org.apache.spark.{SparkEnv, TaskContext} +import org.apache.spark.annotation.Experimental +import org.apache.spark.sql.catalyst.InternalRow +import org.apache.spark.sql.execution.UnaryExecNode +import org.apache.spark.sql.execution.metric.SQLMetric +import org.apache.spark.udf.worker.UDFWorkerSpecification +import org.apache.spark.udf.worker.core.{WorkerSecurityScope, WorkerSession} + +/** + * :: Experimental :: + * Base trait for physical plan nodes that execute UDFs in an external + * worker process via the language-agnostic UDF worker framework. + * + * Dispatchers are obtained via [[SparkEnv#getExternalUDFDispatcher]], + * which uses the [[UDFDispatcherManager]] registered on the + * environment. This avoids serializing the manager as part of the + * physical plan. + */ +@Experimental +trait ExternalUDFExec extends UnaryExecNode { + + /** + * Specification describing how to create and communicate with the UDF worker. + * There is exactly one specification per [[ExternalUDFExec]] node. + */ + def workerSpec: UDFWorkerSpecification + + // --------------------------------------------------------------------------- + // Metrics + // --------------------------------------------------------------------------- + + protected def externalUdfMetrics: Map[String, SQLMetric] = Map( + // TODO [SPARK-55278]: Emit the correct metrics here + ) + + override lazy val metrics: Map[String, SQLMetric] = externalUdfMetrics + + // --------------------------------------------------------------------------- + // Session lifecycle + // --------------------------------------------------------------------------- + + /** + * Creates a [[WorkerSession]] via [[SparkEnv#getExternalUDFDispatcher]] + * and registers cancellation on task failure. The provided function + * receives the session and must return the result iterator. Moreover, + * the function MUST close the session once all input data has been sent. Review Comment: No, we should call close once all the input rows have been sent to the UDF. This is the signal that no more input is to be expected, and the UDF can finish processing after it has consumed all of this data. This is aligned with what we discussed offline earlier today. I changed the comment slightly to make this point clearer. Could you have a look at this new comment? -- 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]
