jerryshao opened a new issue, #14875:
URL: https://github.com/apache/gravitino/issues/14875
### What would you like to be improved?
`docs/lakehouse-generic-delta-table.md` says the `location` property is
required and "must be specified at table level" for external Delta tables, and
its troubleshooting section lists the error `Property 'location' is required
for external Delta tables`.
That is not how the catalog behaves. `GenericCatalogOperations.createTable`
asks the table location provider for a location before it calls
`DeltaTableOperations`. The default provider resolves it from the table
`location`, then the schema `location` + `{table}/`, then the catalog
`location` + `{schema}/{table}/`, and appends a trailing `/`. So:
- Creating a Delta table without `location` succeeds when the schema or
catalog has one, and Gravitino registers the inherited path.
- When no level has a location, the user gets the provider's `'location'
property is neither set in table properties nor in schema properties...` error.
The Delta-specific error listed in the doc cannot be reached through the
catalog.
- The stored `location` may end with a `/`.
### How should we improve?
Update `docs/lakehouse-generic-delta-table.md`:
1. Mark `location` as not strictly required and describe the inheritance by
linking to the location resolution section in `lakehouse-generic-catalog.md`.
Note that a custom `table-location-provider` may resolve it differently.
2. Still recommend setting `location` explicitly for Delta tables. An
inherited path usually has no existing `_delta_log`, and Gravitino does not
check for one.
3. Mention that the stored location may have a trailing `/`.
4. Replace the troubleshooting entry with the error users actually see.
--
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]