danielcweeks opened a new pull request #2855: URL: https://github.com/apache/iceberg/pull/2855
Currently table location placement is somewhat restrictive because the base location is defined by the catalog, but doesn't have all relevant information to construct paths for certain scenarios. The only information available to the catalog is `TableIdentifier`. Adding a TableLocationSupplier interface allows for more information to be used in defining the location of the table and allow for more flexibly layouts that may want to take advantage of other fields that are only populated later in the table creation lifecycle (like uuid, partition spec, sort order, or table properties). Due to the way the table/metadata creation is performed, this is a little difficult to integrate both cleanly and in a backwards compatible way. Posting this as a possible approach to allow for more flexible table layouts. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
