XdithyX opened a new pull request, #55745:
URL: https://github.com/apache/spark/pull/55745
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
This PR replaces `_LEGACY_ERROR_TEMP_3077` with a proper error class,
`MULTIPLE_EVENT_TIME_COLUMNS`([SPARK-55731](https://issues.apache.org/jira/browse/SPARK-55731)).
The error is thrown when a stateful streaming operator receives an input
DataFrame with more than one distinct event-time column while multiple
event-time columns are not allowed.
This PR:
- Adds `MULTIPLE_EVENT_TIME_COLUMNS` to `error-conditions.json`
- Assigns SQLSTATE `42K09`, matching nearby event-time analysis errors
- Updates both throw sites in `WatermarkSupport`
- Updates the existing `EventTimeWatermarkSuite` test to verify the new
error condition
### Why are the changes needed?
`_LEGACY_ERROR_TEMP_3077` is a temporary legacy error class and should be
replaced with a stable, descriptive error class.
The query behavior is already correct. This change improves the structured
error reporting by assigning a real error condition for the multiple event-time
columns case.
### Does this PR introduce _any_ user-facing change?
Yes.
For this error case, the error condition changes from
`_LEGACY_ERROR_TEMP_3077` to `MULTIPLE_EVENT_TIME_COLUMNS`.
The error message remains the same, and the query behavior is unchanged. The
error now also has SQLSTATE `42K09`.
### How was this patch tested?
Tested by running
`build/sbt 'sql / Test / testOnly
org.apache.spark.sql.streaming.EventTimeWatermarkSuite -- -z "multiple event
time columns in an input DataFrame for stateful operator is not allowed"'
`
### Was this patch authored or co-authored using generative AI tooling?
Yes.
--
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]
