[SPARK-57649][SQL][TESTS] Regenerate stale datetime-formatting.sql.out.java21 golden file#56720
Closed
HyukjinKwon wants to merge 1 commit into
Closed
[SPARK-57649][SQL][TESTS] Regenerate stale datetime-formatting.sql.out.java21 golden file#56720HyukjinKwon wants to merge 1 commit into
HyukjinKwon wants to merge 1 commit into
Conversation
…t.java21 golden file
### What changes were proposed in this pull request?
SPARK-57575 added two TIME-type `to_char`/`to_varchar` queries to
`datetime-formatting.sql` and regenerated `datetime-formatting.sql.out` and
`datetime-formatting-legacy.sql.out`, but not the Java 21 variant
`datetime-formatting.sql.out.java21`. This regenerates the Java 21 golden by
appending the two new TIME-type query blocks (their `HH:mm:ss` output is not
locale/JDK sensitive, so it matches the default golden), restoring the expected
36 query blocks.
### Why are the changes needed?
`SQLQueryTestSuite` uses the `.out.java21` golden for any JDK >= 21
(`SQLQueryTestSuite.scala`), so the stale file breaks the scheduled
Maven (Scala 2.13, JDK 21) and JDK 25 builds:
datetime-formatting.sql
Expected 109, but got 103 blocks in result file
'datetime-formatting.sql.out.java21'. Try regenerating the result files.
### Does this PR introduce _any_ user-facing change?
No. Test-only.
### How was this patch tested?
Ran the affected golden tests on JDK 21 and confirmed they pass (see PR description for CI links).
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.8
Co-authored-by: Isaac
Member
Author
|
Self-review (code-review skill, high effort) — posted as a comment, not an approval. Scope: 1 file, +16/-0 (golden test resource only). Findings below. Correctness ✅
Minor note (process /
|
Member
Author
|
Merged to master and branch-4.x. |
HyukjinKwon
added a commit
that referenced
this pull request
Jun 24, 2026
….java21 golden file ### What changes were proposed in this pull request? [SPARK-57575](https://issues.apache.org/jira/browse/SPARK-57575) added two `TIME`-type `to_char`/`to_varchar` queries to `datetime-formatting.sql` and regenerated `datetime-formatting.sql.out` and `datetime-formatting-legacy.sql.out`, but not the Java 21 variant `datetime-formatting.sql.out.java21`. This PR regenerates the Java 21 golden by appending the two new `TIME`-type query blocks (their `HH:mm:ss` output is not locale/JDK sensitive, so it matches the default golden), restoring the expected 36 query blocks. ### Why are the changes needed? `SQLQueryTestSuite` uses the `.out.java21` golden for any JDK >= 21, so the stale file breaks the scheduled **Maven (Scala 2.13, JDK 21)** and **Maven (Scala 2.13, JDK 25)** builds: ``` datetime-formatting.sql Expected 109, but got 103 blocks in result file 'datetime-formatting.sql.out.java21'. Try regenerating the result files. ``` ### Does this PR introduce _any_ user-facing change? No. Test-only. ### How was this patch tested? - **Before (failing job):** [`Build / Maven (Scala 2.13, JDK 21)` → `sql#core - extended tests`](https://github.com/apache/spark/actions/runs/28035705490/job/82998279873) — `datetime-formatting.sql *** FAILED ***`. - **After (passing):** ran `sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z datetime-formatting` on JDK 21 → [✅ all tests passed](https://github.com/HyukjinKwon/spark/actions/runs/28065758228/job/83089561688) (`Tests: succeeded 6, failed 0`). ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.8 Closes #56720 from HyukjinKwon/SPARK-57649-datetime-java21-golden. Authored-by: Hyukjin Kwon <gurwls223@apache.org> Signed-off-by: Hyukjin Kwon <hyukjin.kwon@databricks.com> (cherry picked from commit 7894954) Signed-off-by: Hyukjin Kwon <hyukjin.kwon@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
SPARK-57575 added two
TIME-typeto_char/to_varcharqueries todatetime-formatting.sqland regenerateddatetime-formatting.sql.outanddatetime-formatting-legacy.sql.out, but not the Java 21 variantdatetime-formatting.sql.out.java21. This PR regenerates the Java 21 golden by appending the two newTIME-type query blocks (theirHH:mm:ssoutput is not locale/JDK sensitive, so it matches the default golden), restoring the expected 36 query blocks.Why are the changes needed?
SQLQueryTestSuiteuses the.out.java21golden for any JDK >= 21, so the stale file breaks the scheduled Maven (Scala 2.13, JDK 21) and Maven (Scala 2.13, JDK 25) builds:Does this PR introduce any user-facing change?
No. Test-only.
How was this patch tested?
Build / Maven (Scala 2.13, JDK 21)→sql#core - extended tests—datetime-formatting.sql *** FAILED ***.sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z datetime-formattingon JDK 21 → ✅ all tests passed (Tests: succeeded 6, failed 0).Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.8