jackylee-ch opened a new pull request, #979: URL: https://github.com/apache/paimon-rust/pull/979
MERGE INTO, UPDATE, DELETE, INSERT OVERWRITE and TRUNCATE TABLE all call `ensure_no_time_travel_for_write`, so they cannot commit while the session is pinned to a historical snapshot via a `scan.*` time-travel option. DROP PARTITION also commits a data-deleting snapshot but was missing the check, so `SET 'paimon.scan.snapshot-id' = ...` followed by `ALTER TABLE ... DROP PARTITION` committed against a stale read view instead of being rejected like the other write statements. This calls the same guard at the start of `handle_drop_partitions`, covering both the catalog-managed and write-builder drop paths. Added a test that sets a time-travel option and asserts the drop is rejected; removing the guard makes it fail (the drop otherwise succeeds). -- 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]
