github-actions[bot] commented on issue #737:
URL: https://github.com/apache/iceberg-python/issues/737#issuecomment-2518821922
This issue has been closed because it has not received any activity in the
last 14 days since being marked as 'stale'
--
This is an automated message from the Apac
github-actions[bot] closed issue #737: Support Snapshot Management Operations
URL: https://github.com/apache/iceberg-python/issues/737
--
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 com
github-actions[bot] commented on issue #737:
URL: https://github.com/apache/iceberg-python/issues/737#issuecomment-2489807554
This issue has been automatically marked as stale because it has been open
for 180 days with no activity. It will be closed in next 14 days if no further
activity oc
chinmay-bhat commented on issue #737:
URL: https://github.com/apache/iceberg-python/issues/737#issuecomment-2124351316
@Honah thank you for your response.
I agree that we should hide the `set_ref_snapshot` from the public API. I
also like the idea of creating a `ManageSnapshots` inner cl
HonahX commented on issue #737:
URL: https://github.com/apache/iceberg-python/issues/737#issuecomment-2123759077
Hi @syun64 @chinmay-bhat. Thank you for driving these features. I saw some
PRs raised by @chinmay-bhat : #748, #750, #758. Those are great!
I would like to discuss what AP
chinmay-bhat commented on issue #737:
URL: https://github.com/apache/iceberg-python/issues/737#issuecomment-2113132702
> Yeah I think it would be helpful to introduce a snapshot_by_timestamp
utility function to get the snapshot - just like you mentioned, that would help
recover feature pari
syun64 commented on issue #737:
URL: https://github.com/apache/iceberg-python/issues/737#issuecomment-2113105812
> * How does rollback_to_timestamp use `set_ref_snapshot()`? In the
[rollback_to_timestamp
documentation](https://iceberg.apache.org/docs/1.5.1/spark-procedures/#rollback_to_time
