You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add test for fast-forward behavior after expire_snapshots
Validates that fast-forward still works after expire_snapshots when
the ancestor chain between branch tips remains intact. Documents that
if intermediate snapshots are expired (breaking the chain), fast-forward
would fail — an existing Iceberg behavior unrelated to max-ref-age-ms.
Copy file name to clipboardExpand all lines: integrations/spark/spark-3.5/openhouse-spark-itest/src/test/java/com/linkedin/openhouse/spark/catalogtest/SnapshotExpirationRefsTest.java
+64Lines changed: 64 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -215,6 +215,70 @@ public void testMaxRefAgeMsPropertyDropsExpiredTagAndBranch() throws Exception {
215
215
}
216
216
}
217
217
218
+
/**
219
+
* Validates that fast-forward still works after expire_snapshots has run, as long as the ancestor
220
+
* chain between the target and source branch tips remains intact. This is the CDC blue/green
221
+
* deployment scenario: create a branch, write to it, then fast-forward main.
222
+
*
223
+
* <p>Also validates that if intermediate snapshots on the branch are expired (breaking the
224
+
* ancestor chain), fast-forward fails — demonstrating that expire_snapshots can break
225
+
* fast-forward for long-lived branches with aggressively expired history.
0 commit comments