Yicong-Huang opened a new pull request, #55671: URL: https://github.com/apache/spark/pull/55671
### What changes were proposed in this pull request? Backport of #55494 to branch-4.0. The original change: 1. Renames error class `RESULT_TYPE_MISMATCH_FOR_ARROW_UDF` to `RESULT_COLUMN_TYPES_MISMATCH` (parallel to `RESULT_COLUMN_NAMES_MISMATCH` / `RESULT_COLUMN_SCHEMA_MISMATCH`). 2. Rewords the message from `Columns do not match in their data type: <mismatch>.` to `Column types of the returned data do not match specified schema. Mismatch: <mismatch>.` to align with sibling errors. 3. Removes the dead error class `SCHEMA_MISMATCH_FOR_ARROW_PYTHON_UDF` (already absent on branch-4.0 — no-op for this branch). Branch-4.1 backport: #55670. ### Why are the changes needed? This restores message parity between master server and branch-4.0 client. The scheduled cross-version Connect parity build was failing because master raises the new `RESULT_COLUMN_TYPES_MISMATCH` text while branch-4.0 client tests still assert the old "Columns do not match in their data type" text: https://github.com/apache/spark/actions/runs/25187494316 Backporting keeps the Arrow result-verify error class name and message consistent across maintained branches and unblocks cross-version parity tests. ### Conflicts resolved - `python/pyspark/errors/error-conditions.json`: kept `RETRIES_EXCEEDED` entry (only present on branch-4.0). - `python/pyspark/sql/tests/arrow/test_arrow_grouped_map.py`: kept the branch-4.0 `lambda table: table` direct call form (master uses a `function_variations(...)` loop helper that is not present on branch-4.0); only the assertion message text is updated. ### Does this PR introduce _any_ user-facing change? Yes (same as #55494). User-visible error class name and message for result column type mismatches in Arrow UDFs change on branch-4.0. ### How was this patch tested? Existing tests; updated 4 asserts in `test_arrow_grouped_map.py` / `test_arrow_cogrouped_map.py` match the new message. ### 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]
