rdblue commented on issue #253: Register existing tables in Iceberg HiveCatalog URL: https://github.com/apache/incubator-iceberg/pull/253#issuecomment-514761974 > Of course, having a way to roll back the entire table state and minimizing changes to the Catalog API are reasonable benefits. The drawback is that we will have to create a separate instance of HiveTableOperations with its own HMS client pool. Why is this? Wouldn't the table use the client pool from the Catalog instance? I think `TableOperations` is exposed from `BaseTable`, right? So as long as you are using the `HiveCatalog`, you'd get a table with an accessible operations object. To avoid the issue of a table being available before the metadata is replaced, we should add the create/replace transaction methods to `Catalog`. We'll need those for atomic operations anyway.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
