-
Notifications
You must be signed in to change notification settings - Fork 28.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-44113][BUILD][INFRA][DOCS] Drop support for Scala 2.12 #43008
Conversation
@@ -19,7 +19,7 @@ | |||
|
|||
set -e | |||
|
|||
VALID_VERSIONS=( 2.12 2.13 ) | |||
VALID_VERSIONS=( 2.13 ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No further modifications were made to this file, just made Scala-2.12 an invalid option. We can refactor this script in the future when we need to support multiple Scala versions again.
cc @dongjoon-hyun FYI Do we need to further split this PR ? If you think this PR is too bloated, I can split into separate prs. |
I'm good with this single PR. Could you resolve the conflict? |
done ~ |
cc @HyukjinKwon , @srowen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM (from my side)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think this is OK if tests pass. We can next look at making minor code changes that were hard or not possible while supporting 2.13, on the way to looking at supporting Scala 3.
Could you re-trigger the failed pipeline, @LuciferYang ? |
GA passed: https://github.com/apache/spark/runs/17002787095 |
jline/3.22.0//jline-3.22.0.jar | ||
jna/5.13.0//jna-5.13.0.jar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do they become runtime deps now?
And since both jline 2 and 3 are present at the classpath, is it safe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's fine then, thanks for checking
Co-authored-by: Cheng Pan <[email protected]>
Merged to master. Thank you, @LuciferYang and all. |
@@ -26,8 +26,8 @@ | |||
curr_dir = pwd | |||
cd("..") | |||
|
|||
puts "Running 'build/sbt -Pkinesis-asl clean compile unidoc' from " + pwd + "; this may take a few minutes..." | |||
system("build/sbt -Pkinesis-asl clean compile unidoc") || raise("Unidoc generation failed") | |||
puts "Running 'build/sbt -Pscala-2.13 -Pkinesis-asl clean compile unidoc' from " + pwd + "; this may take a few minutes..." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QQ, why do we need scala profile here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we execute dev/change-scala-version.sh 2.13
, it simultaneously modifies both copy_api_dirs.rb
and mima
files, adding these -Pscala-2.13
. In this PR, I didn't clean them up. It seems we could add a follow-up to clear these unnecessary -Pscala-2.13
.
### What changes were proposed in this pull request? This PR is a followup of #43008 that removes the leftover scheduled GitHub Actions build for Scala 2.13 scheduled build. ### Why are the changes needed? After dropping Scala 2.12, the default build is exactly same as the scheduled job for Scala 2.13 now. ### Does this PR introduce _any_ user-facing change? No, dev-only. ### How was this patch tested? Will monitor the scheduled builds. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #43047 from HyukjinKwon/SPARK-44113-folliwup. Authored-by: Hyukjin Kwon <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Thanks all ~ |
…nts, and scala-2.13 profile usage ### What changes were proposed in this pull request? This PR is a followup of #43008 that cleanups Scala version specific comments, and `scala-2.13` profile usage. See also #43008 (comment) ### Why are the changes needed? To remove unnecessary profile specifications ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI in this PR should test them out. For README.md, I manually checked via GitHub. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #43049 from HyukjinKwon/SPARK-44113-followup-2. Authored-by: Hyukjin Kwon <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
The main purpose of this PR is to remove support for Scala 2.12 in Apache Spark 4.0, the specific work includes:
dev/change-scala-version.sh 2.13
to change the Scala version in allpom.xml
files to 2.13pom.xml
configuration related to Scala 2.12 and set the Scala 2.13 configuration as the defaultSparkBuild.scala
python/run-tests.py
anddev/run-tests.py
docs/building-spark.md
,docs/index.md
,docs/spark-connect-overview.md
,docs/storage-openstack-swift.md
,docs/_config.yml
to Scala 2.13dev/test-dependencies.sh
,dev/scalafmt
,dev/mima
,dev/lint-scala
to Scala 2.13dev/change-scala-version.sh
and cleaned up its invocation in Spark codedev/deps/spark-deps-hadoop-3-hive-2.3
andLICENSE-binary
scala-213
frombuild_and_test.yml
because the daily test of other branches will not run this task, and the master branch already uses Scala 2.13 by default.name
of the following.yml
files:build_ansi.yml
,build_coverage.yml
,build_java11.yml
,build_java17.yml
,build_java21.yml
,build_maven.yml
, andbuild_rockdb_as_ui_backend.yml
benchmark.yml
src/scala-2.13/
directory tosrc/main/scala
and deleted all files in thesrc/scala-2.12/
directory.load-spark-env.cmd
andload-spark-env.sh
.build-helper-maven-plugin
configurations fromcore/pom.xml
,repl/pom.xml
,sql/api/pom.xml
,sql/catalyst/pom.xml
,sql/core/pom.xml
andconnector/connect/common/pom.xml
Why are the changes needed?
The minimum supported Scala version for Apache Spark 4.0 is Scala 2.13.
Does this PR introduce any user-facing change?
Yes, Apache will no longer support Scala 2.12
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No