Open-API: Slim down REST fixture shadow JAR and externalize cloud bundles#16214
Draft
kevinjqliu wants to merge 3 commits intoapache:mainfrom
Draft
Open-API: Slim down REST fixture shadow JAR and externalize cloud bundles#16214kevinjqliu wants to merge 3 commits intoapache:mainfrom
kevinjqliu wants to merge 3 commits intoapache:mainfrom
Conversation
Co-authored-by: Copilot <copilot@github.com>
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.
Changes
(iceberg-aws, iceberg-gcp, iceberg-azure, iceberg-bigquery) and JUnit dependencies
from the shadow JAR.
-cpinstead of-jar) sothey can be included/excluded independently.
REST_PORTenv var — renamed toCATALOG_REST_PORTso the server actuallyreads it through the
CATALOG_*environment mapping.Motivation
The shadow JAR previously bundled all cloud provider SDKs (AWS, GCP, Azure) directly,
making it unnecessarily large. Cloud bundles are already published as standalone JARs and
can be loaded at runtime via the classpath, matching how they're consumed in Spark/Flink.
Testing
CATALOG_REST_PORT=8183— server starts, serves/v1/config,creates/lists namespaces