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 2022/05/02 18:43:44 UTC

[GitHub] [iceberg] flyrain commented on pull request #4681: Core: Log the new metadata location in commit.

flyrain commented on PR #4681:
URL: https://github.com/apache/iceberg/pull/4681#issuecomment-1115236877

   > I'm not sure we want to force all future table operations to include a literal location (or have to return one). So we may want to have the logging in the operations (HiveTableOperations, HadoopTableOperations, ... ) themselves?
   
   Good point. But I think a table version string will be there even for a future catalog without a metatdata.json file. It can easily support that, with minor word change. like `Successfully committed to table {} with the new metadata location({})` -> `Successfully committed to table {} with the new version ({})`
   
   Hi @kbendick, what do you think from the perspective of rest API catalog?


-- 
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