This is an automated email from the ASF dual-hosted git repository.

ruifengz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new f48de1015470 [SPARK-53592][PYTHON][TESTS][FOLLOW-UP] Remove unused 
config in the parity test
f48de1015470 is described below

commit f48de101547063e266d5e94b8bc9949b0e5fd39d
Author: Ruifeng Zheng <[email protected]>
AuthorDate: Mon Sep 22 15:47:03 2025 +0800

    [SPARK-53592][PYTHON][TESTS][FOLLOW-UP] Remove unused config in the parity 
test
    
    ### What changes were proposed in this pull request?
    Remove unused config in the parity test
    
    ### Why are the changes needed?
    this config is not used
    
    ### Does this PR introduce _any_ user-facing change?
    no, test-only
    
    ### How was this patch tested?
    ci
    
    ### Was this patch authored or co-authored using generative AI tooling?
    no
    
    Closes #52403 from zhengruifeng/udf_test_followup.
    
    Authored-by: Ruifeng Zheng <[email protected]>
    Signed-off-by: Ruifeng Zheng <[email protected]>
---
 python/pyspark/sql/tests/connect/test_parity_unified_udf.py | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/python/pyspark/sql/tests/connect/test_parity_unified_udf.py 
b/python/pyspark/sql/tests/connect/test_parity_unified_udf.py
index 8c076f173c95..d89bf0fc1b93 100644
--- a/python/pyspark/sql/tests/connect/test_parity_unified_udf.py
+++ b/python/pyspark/sql/tests/connect/test_parity_unified_udf.py
@@ -22,10 +22,7 @@ from pyspark.testing.connectutils import 
ReusedConnectTestCase
 
 
 class UnifiedUDFParityTests(UnifiedUDFTestsMixin, ReusedConnectTestCase):
-    @classmethod
-    def setUpClass(cls):
-        ReusedConnectTestCase.setUpClass()
-        cls.spark.conf.set("spark.sql.execution.pythonUDF.arrow.enabled", 
"false")
+    pass
 
 
 if __name__ == "__main__":


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

Reply via email to