[GitHub] [iceberg] jackye1995 commented on pull request #6179: AWS: Re-tag files when renaming tables in GlueCatalog

[GitBox <gi...@apache.org>]

jackye1995 commented on PR #6179:
URL: https://github.com/apache/iceberg/pull/6179#issuecomment-1382318184

   I'd like to discuss this a bit more, since we do have some actual customer use cases for this, because overall the S3 tagging related features in Iceberg integrate very well with S3 lifecycle policy and bucket permission, RENAME seems to be the only piece that is missing for the whole end to end flow to work.
   
   > I think that if a rename requires anything but a metadata operation, then the Iceberg catalog should not allow it and should throw an exception that rename is not supported.
   
   Totally agree. The reason I was relatively not against this approach was that RENAME is not a frequent operation for most users, and they are willing to wait long to complete the full rename if it can update related tags or other metadata information in storage.
   
   > Users aren't going to know that this is needs to perform a potentially huge number of S3 operations. 
   
   Correct, maybe one way to resolve this is to throw exception by default and user has to turn on the feature to be aware of the implications.
   
   This logic will probably exist outside Iceberg repository if it is not contributed in. @rdblue please let me know if there is any intermediate grounds that could be taken for this use case.


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