Yicong-Huang opened a new pull request, #58108:
URL: https://github.com/apache/spark/pull/58108

   ### What changes were proposed in this pull request?
   
   Register `UDF` as a primary component in the `dev/merge_spark_pr.py` 
component registry:
   
   ```python
   Component("UDF", primary=True, jira_name="UDF"),
   ```
   
   The registry is kept in sync with the SPARK JIRA component list, and `UDF` 
(JIRA component "UDF", i.e. Frictionless UDF) was missing from it. It is 
inserted in alphabetical order between `TEST` and `UI` and marked 
`primary=True`, matching other functional API areas such as `SQL`, `PYTHON`, 
and `ML`. Doctests are added covering `Component.find("UDF")` and the JIRA-name 
mapping via `jira_components_from_title_tags(["UDF"])`.
   
   ### Why are the changes needed?
   
   The merge script requires every PR title to carry at least one primary 
component tag, and reconciles a PR title's tags against the linked JIRA's 
components. Because `UDF` was absent from the registry, a PR titled e.g. 
`[SPARK-XXXXX][UDF] ...` had its `[UDF]` tag ignored during JIRA component 
reconciliation and was rejected at merge time for lacking a primary tag, 
forcing the committer to add another tag. `UDF` is a legitimate, substantive 
SPARK JIRA component, so it should stand on its own like the other functional 
areas. This mirrors the recent [SPARK-58638] which recognized `EXAMPLES` as a 
primary component tag.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. This only affects the committer-facing merge tooling.
   
   ### How was this patch tested?
   
   Added inline doctests and ran the module's doctest suite:
   
   ```
   $ python -m doctest dev/merge_spark_pr.py && echo ok
   ok
   ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   No.
   


-- 
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