rangareddy commented on issue #16132:
URL: https://github.com/apache/hudi/issues/16132#issuecomment-5469440138
This issue was reviewed as part of the JIRA-migrated backlog triage
(HUDI-6602).
**Findings: obsolete. Closing.**
The ask was to extend the docker Java 17 test to Spark 3.3, since at filing
time it covered only "Spark 3.4+".
On `master` the Java 17 lane has moved in the opposite direction. In
`.github/workflows/bot.yml`, `test-spark-java17-java-tests-part1` (line 719)
and `part2` (line 781) run **only** `sparkProfile: spark4.2` with `scala-2.13`
- the `spark3.5`, `spark4.0` and `spark4.1` matrix entries are all commented
out:
```yaml
# - scalaProfile: "scala-2.13"
# sparkProfile: "spark3.5"
# - scalaProfile: "scala-2.13"
# sparkProfile: "spark4.0"
# - scalaProfile: "scala-2.13"
# sparkProfile: "spark4.1"
- scalaProfile: "scala-2.13"
sparkProfile: "spark4.2"
```
Spark 3.3 is still exercised in `bot.yml` (15 occurrences), but under the
Java 8/11 lanes - the supported pairing for that line.
So adding a Java 17 x Spark 3.3 cell now would mean testing a legacy Spark
line under a JDK lane that has deliberately moved past it. Closing as no longer
applicable rather than leaving it in the backlog as apparent pending work.
Happy to reopen if the Java 17 matrix is deliberately widened back down the
Spark 3.x range.
--
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]
