jiangxt2 opened a new pull request, #13423: URL: https://github.com/apache/gravitino/pull/13423
### What changes were proposed in this pull request? - Add the Lance Namespace `RenameTable` REST endpoint and route same-schema and cross-schema requests through Gravitino's existing table-rename operation. - Rename Gravitino metadata without opening or moving the Lance dataset. Preserve its location, data, table properties, and stored `lance.version`; let the table identifier and normal Gravitino audit metadata follow existing rename semantics. - Check source-table modification and destination-schema table-creation permissions for cross-schema renames, and map failures to Lance-compatible errors. ### Why are the changes needed? Lance Spark's REST namespace catalog uses `RenameTable` for `ALTER TABLE ... RENAME TO ...`, but Gravitino's Lance REST service did not expose this operation. This change enables that Spark REST flow without moving or rewriting Lance data. Fix: #13392 ### Does this PR introduce _any_ user-facing change? Yes. Users can rename Lance tables through the Gravitino-backed Lance REST catalog, including across schemas within the same Gravitino catalog. ### How was this patch tested? - `TestGravitinoLanceTableOperations` and `TestLanceTableOperations`. - Targeted REST rename success and failure integration tests. - `LanceTableAuthorizationIT.testCrossSchemaRenameRequiresDestinationCreateTable`. - `LanceSparkRESTServiceIT.testRenameTableViaSpark` with `lance-spark-bundle` 0.5.1. - Spotless formatting and `git diff --check`. The full REST service suite was not rerun on the final patch; the targeted tests listed above passed. -- 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]
