edgarRd opened a new pull request, #4715: URL: https://github.com/apache/iceberg/pull/4715
While the WAP workflow enables users to write data via SQL using a `wap_id`, there's a lack in usability when applying those changes written to the table during the Publish step of the workflow. The user needs to figure out the `snapshot-id` programmatically to cherry-pick the changes. Ideally, we should have all steps of the WAP workflow available via SQL, since Iceberg has the `wap-id => snapshot-id` mapping in its own metadata. This PR proposes a SQL procedure to cherry-pick the changes created with a `wap-id`. Functionally, it works the same as the cherry-pick procedure, but receives a `wap-id` as argument instead of a `snapshot-id`. This would make the Write and Publish parts of WAP available via SQL. The procedure name proposed is `publish_changes` but I'm open to suggestions if another name would fit better. Thanks. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
