Add Polaris Community Meetings for 2026-01-22 and 2026-02-05#3715
Merged
jbonofre merged 1 commit intoapache:mainfrom Feb 9, 2026
Merged
Add Polaris Community Meetings for 2026-01-22 and 2026-02-05#3715jbonofre merged 1 commit intoapache:mainfrom
jbonofre merged 1 commit intoapache:mainfrom
Conversation
dimas-b
reviewed
Feb 9, 2026
adutra
approved these changes
Feb 9, 2026
dimas-b
approved these changes
Feb 9, 2026
snazy
added a commit
to snazy/polaris
that referenced
this pull request
Feb 11, 2026
* "Stale" job: don't close stale issues (apache#3683) This PR also fixes the configuration and upgrades the action to the latest version. * Fix integration-tests after apache#3704 (apache#3711) Short story: This change fixes the int-tests in `:polaris-runtime-service`. Long story is this: In `:polaris-runtime-service` we intentionally declare "just" a `platform(libs.quarkus.bom)` dependency, because of the `:polaris-spark-integration-*` module. It is however generally recommended by Quarkus to _only_ use `enforcedPlatform(libs.quarkus.bom)` to effectively prevent breaking changes coming from transitive dependencies. Which is exactly what happend after apache#3704. Why did CI not catch this issue? The answer is pretty simple: The effective Gradle task inputs, including the `intTestRuntimeClasspath` did not change. So the previously cached test outcomes could be reused, and the int-tests did not run. Just adding the `runtimeClasspath` as another task-input of the `intTest` may _not_ work as intended. Why does _removing_ `implementation(platform(libs.opentelemetry.bom))` help? Simply because that lets the dependencies fall back to to the declared transitive dependencies. We do not have direct dependencies to OTel. The correct fix here _would_ be to use `implementation(enforcedPlatform(libs.quarkus.bom))`, but that breaks the Spark plugin integration tests. There is a better alternative: Let the Spark plugin tests leverage polaris-apprunner, which is meant for exactly the use case of effectively decoupling some module from the build requirements of a Quarkus application. * CI: fix missing Gradle build scans (apache#3709) Publishing the Gradle build scans requires the `DEVELOCITY_ACCESS_KEY` secret. For workflow-calls, each secret to be propagated to a called workflow must be explicitly defined. This change propagates the secrets from `ci-main.yml` to the called `ci.yml`. * Add Polaris Community Meetings for 2026-01-22 and 2026-02-05 (apache#3715) * Add location propertiesfrom TableMetadata into Table entity internalProperties (apache#3226) * Compile client modules with Java 17 compatibility (apache#3712) * Last merged commit ba048c8 --------- Co-authored-by: Alexandre Dutra <[email protected]> Co-authored-by: JB Onofré <[email protected]> Co-authored-by: Prashant Singh <[email protected]>
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.
No description provided.