jiangxt2 opened a new issue, #13392: URL: https://github.com/apache/gravitino/issues/13392
### Describe the feature Support `ALTER TABLE ... RENAME TO ...` for Lance tables accessed through Gravitino's Lance REST namespace. Support renames within the same Gravitino catalog, including renames within a schema and across schemas. A successful rename should update the table identifier in the namespace while keeping the existing Lance dataset accessible under the new identifier. ### Motivation Lance Spark supports table rename for namespace-based catalogs configured with `impl=rest` by calling the Lance Namespace `RenameTable` operation. Gravitino's Lance REST service does not currently expose this operation, so table rename cannot be completed through a Gravitino-backed Lance REST catalog. ### Describe the solution Implement the standard Lance Namespace `RenameTable` operation in Gravitino's Lance REST service and route it through Gravitino's existing table-rename path. The operation should not move, copy, or rewrite the underlying Lance dataset. It should preserve the dataset location and data, and follow Gravitino's existing metadata and authorization semantics. Return compatible errors when the source table does not exist, the target already exists, or the caller is not authorized. ### Additional context - Lance Namespace defines `RenameTable`, and the Lance Spark REST namespace catalog calls `namespace.renameTable()`. - Gravitino's current Lance table alteration path does not handle `TableChange.RenameTable`. - Gravitino #13303 tracks broader metadata identity consistency; its cross-schema authorization subtask #13310 was addressed by merged PR #13316. This request is specifically about the missing Lance REST `RenameTable` operation. - Path-based rename and moving tables between different Gravitino catalogs are out of scope. -- 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]
