diqiu50 opened a new pull request, #12997: URL: https://github.com/apache/gravitino/pull/12997
### What changes were proposed in this pull request? `GlueCatalogOperations.resolveTableLocation` now uses the `LocationUri` declared by the Glue database as the base for a table that is created without an explicit `location` property, and falls back to the catalog `warehouse` property only when the database declares no location. ### Why are the changes needed? The table location was always derived as `warehouse/database/table`, so tables Gravitino created sat under a different prefix from tables other tools created in the same Glue database, and a catalog whose `warehouse` was set to the database's own location produced a doubled database segment in the path. Fix: #12996 ### Does this PR introduce _any_ user-facing change? Yes, a table created in a Glue database that declares a `LocationUri` is now placed under that URI instead of under the catalog warehouse; no property is added or removed, and existing data is not moved. ### How was this patch tested? Added unit tests in `TestGlueCatalogTableOperations` covering the database location, a trailing slash on it, the warehouse fallback, an explicit `location` property and a failed database lookup, and ran `./gradlew :catalogs:catalog-glue:test -PskipITs` together with `./gradlew spotlessApply`. -- 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]
