You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yicong Huang (Jira)" <ji...@apache.org> on 2026/08/19 20:11:00 UTC
[jira] [Resolved] (SPARK-58862) Recognize UDF as a primary component tag in the merge script
[ https://issues.apache.org/jira/browse/SPARK-58862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yicong Huang resolved SPARK-58862.
----------------------------------
Fix Version/s: 5.0.0
Resolution: Fixed
Issue resolved by pull request 58108
[https://github.com/apache/spark/pull/58108]
> Recognize UDF as a primary component tag in the merge script
> ------------------------------------------------------------
>
> Key: SPARK-58862
> URL: https://issues.apache.org/jira/browse/SPARK-58862
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 5.0.0
> Reporter: Yicong Huang
> Assignee: Yicong Huang
> Priority: Major
> Labels: pull-request-available
> Fix For: 5.0.0
>
>
> The merge script dev/merge_spark_pr.py keeps a registry of SPARK JIRA components and requires every PR title to carry at least one primary component tag. The UDF component (JIRA component "UDF", i.e. Frictionless UDF) was missing from the registry entirely, so a PR titled e.g. [SPARK-XXXXX][UDF] ... has its [UDF] tag ignored during JIRA component reconciliation and is rejected at merge time for lacking a primary tag. This registers UDF and marks it primary, consistent with other functional API areas (SQL, PySpark, ML), so [UDF] resolves to the "UDF" JIRA component and satisfies the merge-time requirement on its own.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org