dramaticlly commented on issue #12134: URL: https://github.com/apache/iceberg/issues/12134#issuecomment-2649328210
> I added this on the mailing list but thought I'd drop it here as well: > > I think the issue here is that you're using the commit api in table operations to perform a non-incremental/linear change to the metadata. The REST implementation is a little more strict in that it builds a set of updates based on the mutations made to the metadata and the commit process applies those changes. In this scenario, no changes have been made and the call is attempting a complete replacement. > > The other implementations are just blindly swapping the location, so while that operation does achieve the effect you're looking for, it's not the right semantics for the commit. > > You might want to consider using the "register table" operation instead, which takes the table identifier and location to perform this type of swap. Thank you @danielcweeks for the detailed reply. I actually trying to rely on this as a replacement for "drop + register table" operation as TableOperations.commit can be done atomically suggested by @rdblue way back in https://github.com/apache/iceberg/pull/5327#issuecomment-1207478697. -- 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-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
