Skip to content

Conversation

@a10y
Copy link
Contributor

@a10y a10y commented Jan 13, 2026

Tested using our existing unit tests.

We could create a separate vortex-spark3 and vortex-spark4 repo if we really wanted to go the extra mile but I think that's not necessary until someone comes yelling about Spark 3 support.

This switches our JARs to build for minimum Java 17 and Spark 4 deprecates support for Scala 2.12

@a10y a10y added the feature Release label indicating a new feature or request label Jan 13, 2026
@a10y a10y changed the title spark 4.1.0 Spark 4 Jan 13, 2026
@codecov
Copy link

codecov bot commented Jan 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.45%. Comparing base (d757be1) to head (6d213bd).

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Signed-off-by: Andrew Duffy <[email protected]>

---

Your goal is to upgrade this repository to the latest Spark V4 release.

There is a multi-project Gradle build inside of the @java folder, which
currently targets Spark 3.5.7

Make any changes needed in the @java/vortex-spark subproject to allow us to start publishing
a new JAR for Spark v4

Use Scala 2.12

We use the `com.palantir.consistent-versions` gradle plugin for managing dependencies using the @java/versions.props file
to declare version pins.

If you update a version pin or add/remove a dependency, run `./gradelw --write-locks` from inside of @java to update the `@java/versions.lock file

Use the installed JDK from the environment to run Gradle.

To run unit tests:

    ./gradlew vortex-spark:test

All gradle commands should be run from inside the @java folder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Release label indicating a new feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants