rdblue commented on issue #11103: URL: https://github.com/apache/iceberg/issues/11103#issuecomment-2353618049
> The problem really is: the current RESTCatalog client implementation will **NOT** honor the `last-updated-ms` field passed back by REST server, and instead override the `last-updated-ms` field with client side timestamp before passing back to Spark optimizer/executor. This doesn't sound like the right behavior to me, but I want to check if that's actually the intentional behavior. The problem is less about what makes a "right" timestamp in that sense. I've been talking with with @haizhou-zhao on Slack and I think this is the correct issue to look into. The REST service _should_ update the timestamp when it writes and commits metadata using the changes sent from the client. But the REST client should not modify the timestamp that it receives from the service. I suspect this is happening when the metadata is rebuilt to add the metadata location. -- 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
