Introduce Rolling forward to snapshot with Presto Procedure on Iceberg table

[Hank27-zhang]

Description

The current existing pedicure rollback_to_snapshot (https://prestodb.io/docs/current/connector/iceberg.html#id2) in the Iceberg connector allows only rolling forward to an old snapshot but we can't roll forward to a different snapshot of ta Iceberg Table. Update the API to support roll-forward as well.
Related issue: #20881

Test Plan

update IcebergDistributedSmokeTestBase.testRollbackSnapshot()

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

Iceberg Changes
*Rolling forward to snapshot with Presto Procedure on Iceberg table

If release note is NOT required, use:

== NO RELEASE NOTE ==

[linux-foundation-easycla]

• ❌ - login: @Hank27-zhang . The commit (e069fb5) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[imjalpreet]

On looking at spark procedures in the official iceberg documentation, I feel Presto should be in sync with them so that the users who use spark as well are not confused with the working of each of them.

Spark has two separate procedures for rollback_to_snapshot (https://iceberg.apache.org/docs/1.3.1/spark-procedures/#rollback_to_snapshot) and set_current_snapshot (https://iceberg.apache.org/docs/1.3.1/spark-procedures/#set_current_snapshot).

I had a look at their implementation and they use manageSnapshots().rollbackTo in the case of rollback_to_snapshot and manageSnapshots().setCurrentSnapshot in the other case.

rollback_to_snapshot: https://github.com/apache/iceberg/blob/master/spark/v3.1/spark/src/main/java/org/apache/iceberg/spark/procedures/RollbackToSnapshotProcedure.java#L88C67-L88C67

set_current_snapshot: https://github.com/apache/iceberg/blob/master/spark/v3.1/spark/src/main/java/org/apache/iceberg/spark/procedures/SetCurrentSnapshotProcedure.java#L89

IMO we should also introduce another procedure for setCurrentSnapshot rather than updating the current procedure.

[imjalpreet]

• ❌ - login: @Hank27-zhang . The commit (e069fb5) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

Also, please sign the CLA.

[agrawalreetika]

Hi @Hank27-zhang,
Even I think adding a separate procedure set_current_snapshot for setting snapshot would be better and keep the existing one as it is. Please let us know what you think about that.

[tdcmeehan]

@Hank27-zhang are you still working on this?

[agrawalreetika]

Closing this in favour of #23567