You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2021/07/19 17:20:17 UTC

[GitHub] [iceberg] rdblue commented on issue #2833: Unified syntax for system table names

rdblue commented on issue #2833:
URL: https://github.com/apache/iceberg/issues/2833#issuecomment-882721921


   @pvary, in Spark the rules are:
   
   1. If the name has one identifier part, then use the current catalog and namespace with identifier as the table name
   2. If the multi-part identifier does not start with a catalog name, use the current catalog with the identifier's namespace and table name
   3. If the multi-part identifier starts with a catalog name, it is a full identifier. Use the catalog, namespace, and table name from the identifier
   
   Those never produce ambiguity. The trade-off is that if you use a table name like `customers.history` (where `customers` is a table) then Spark will not fill in the current database/schema name for the namespace. Spark would be able to find `customers` and resolve it to `current_catalog.current_namespace.customers` though.


-- 
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: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org