jiangxt2 opened a new pull request, #13170: URL: https://github.com/apache/gravitino/pull/13170
### What changes were proposed in this pull request? Align the default Lance Spark compatibility validation with the declared Gravitino 1.3.0 support matrix. When no `lanceSparkBundleVersions` property is supplied, the normal Lance REST integration test now uses the declared and tested `0.5.1` bundle as its primary baseline, while `lanceSparkMatrixTest` covers `0.2.0`, `0.4.0`, and `0.5.1`. Explicit `-PlanceSparkBundleVersions=...` values remain targeted diagnostic overrides; the supplied list is used as the matrix and its first version remains the primary for the normal `test` task. The existing per-version configurations, bundle preparation tasks, isolated classloader, version-specific reports, and serial matrix execution are preserved. The Spark integration example is updated to use the `0.5.1` bundle. No production REST code, dependency version, or workflow change is included. ### Why are the changes needed? The Gravitino 1.3.0 documentation and compatibility workflow declare `0.2.0`, `0.4.0`, and `0.5.1` as the verified Lance Spark releases, but the Gradle no-property fallback currently contains only `0.4.0` and also derives the normal test primary from the first list item. This makes the default Gradle validation inconsistent with the declared compatibility contract and leaves the normal test path behind the declared `0.5.1` baseline. This change separates the no-property primary selection from matrix ordering while retaining the existing diagnostic override behavior. No Issue is referenced because this is a standalone validation-policy alignment for an existing capability, not a production bug fix. The baseline is `0.5.1`, the newest release in that matrix; newer releases such as `0.7.1` are outside the declared contract and require a separate support decision. ### Does this PR introduce _any_ user-facing change? No public API, REST protocol, production handler, dependency version, or workflow behavior is changed. The integration documentation now shows the `0.5.1` Spark bundle as the primary example. ### How was this patch tested? - `./gradlew :lance:lance-rest-server:spotlessKotlinGradleCheck -PskipWeb=true -PskipDockerTests=true --no-daemon --console=plain` — passed. - Gradle `--dry-run` task-graph checks for the default primary, default matrix, single-version override, and reordered override — passed. - `./gradlew :lance:lance-rest-server:test --tests '*LanceSparkRESTServiceIT*' -PskipDockerTests=true -PskipWeb=true --no-daemon --console=plain` — passed; 13 tests, 0 skipped tests, 0 failures, 0 errors against the default `0.5.1` primary. - `./gradlew :lance:lance-rest-server:lanceSparkMatrixTest -PskipDockerTests=true -PskipWeb=true --no-daemon --console=plain` — passed; `0.2.0`, `0.4.0`, and `0.5.1` each ran 13 tests with 0 skipped tests, 0 failures, 0 errors. - `./gradlew :docs:build -PskipWeb=true -PskipDockerTests=true --no-daemon --console=plain` — passed. The Lance Spark integration checks use the embedded test mode with Docker-tagged tests skipped; they do not claim multi-container deployment coverage. -- 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]
