lasdf1234 opened a new pull request, #11219:
URL: https://github.com/apache/gravitino/pull/11219

   ### What changes were proposed in this pull request?
   
   Upgrade Gravitino's server-side Apache Iceberg dependency from **1.10.1** to 
**1.11.0** for the Iceberg REST Catalog (IRC) service and lakehouse Iceberg 
catalog modules.
   
   Key changes:
   
   - Bump `iceberg` version in `gradle/libs.versions.toml` to `1.11.0`.
   - Adapt IRC REST handlers to Iceberg 1.11 APIs (e.g. 
`CatalogHandlers.loadTable` with `SnapshotMode.ALL`, namespace encode/decode 
via `RESTUtil` through `IcebergRESTUtils`).
   - Build `PlanTableScanResponse` in `CatalogWrapperForREST` using 
`PlanTableScanResponse.builder().withFileScanTasks(...).withSpecsById(table.specs())`,
 aligned with Iceberg `CatalogHandlers.planTableScan`.
   - Update lakehouse Iceberg tests and IRC REST tests for 1.11 compatibility.
   - Update docs (`iceberg-rest-service.md`, `lakehouse-iceberg-catalog.md`, 
`docker-image-details.md`) for Iceberg 1.11.0.
   
   ### Why are the changes needed?
   
   Iceberg 1.11 updates REST catalog behavior and APIs. Staying on 1.10.1 
blocks alignment with 1.11 clients and the current REST spec.
   
   Fix: #(issue)
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes, documentation reflects Iceberg **1.11.0** for IRC and lakehouse Iceberg 
catalog. Scan-plan responses use the same Iceberg builder path as upstream 
`CatalogHandlers` (wire format unchanged).
   
   ### How was this patch tested?
   
   - `./gradlew :iceberg:iceberg-rest-server:compileJava 
:iceberg:iceberg-rest-server:compileTestJava -PskipITs`
   - `./gradlew :iceberg:iceberg-rest-server:test -PskipITs --tests 
org.apache.gravitino.iceberg.service.TestCatalogWrapperForREST --tests 
org.apache.gravitino.iceberg.service.rest.TestScanPlanCache`
   
   
   Made with [Cursor](https://cursor.com)


-- 
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]

Reply via email to