Skip to content

[Spark] Add AMT variants of the DELETE test suites - #7849

Merged
murali-db merged 2 commits into
delta-io:masterfrom
geraintcjy:add-amt-variants-of-delete-suites
Oct 15, 2026
Merged

murali-db merged 2 commits into
delta-io:masterfrom
geraintcjy:add-amt-variants-of-delete-suites

Conversation

@geraintcjy

@geraintcjy geraintcjy commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Which Delta project/connector is this regarding?

  • Spark
  • Standalone
  • Flink
  • Kernel
  • Other (fill in here)

Description

Adds DeleteAMT and RowTrackingDeleteAMT dimensions to the delta-suite-generator, plus a generated deleteamt group that runs the DELETE tests against AMT (adaptiveMetadata-preview) tables, following the UPDATE AMT suites.

  • DeleteAMTMixin brackets each executeDelete with the AMTDMLTestUtils checkpoints. RowTrackingDeleteAMTMixin brackets each test table's body instead, since its row tracking checks inspect the latest commit.
  • AMT requires deletion vectors, so AMTDMLTestUtils now unsets a suite's delta.enableDeletionVectors = false default for new tables for all AMT DML suites (moved from the UPDATE AMT base), and keeps DELETE, UPDATE and MERGE from writing deletion vectors where the tests assert file rewrites.
  • The DELETE schema pruning tests only collect scans over a TahoeFileIndex, so they skip the checkpoint's tree read.
  • Excludes the tests the row tracking and deletion vector DELETE suites already exclude, and the row tracking tests that create tables with row tracking disabled, which AMT rejects. RowTrackingDeleteDvBase is not generated, since its only test disables deletion vectors on new tables.

How was this patch tested?

Test-only change. The new generated deleteamt suites run the existing DELETE tests on AMT tables.

Does this PR introduce any user-facing changes?

No.

… tests

- Move the rule that unsets a suite's `delta.enableDeletionVectors = false` default for new
  tables from the UPDATE and DELETE AMT bases into `AMTDMLTestUtils`. When it applies, keep
  DELETE, UPDATE and MERGE from writing persistent deletion vectors, so tests that predict file
  rewrites from that default still hold.
- The DELETE schema pruning tests now only collect scans over a `TahoeFileIndex`, which skips the
  AMT tree read, so the AMT DELETE suites no longer exclude them.
@murali-db
murali-db merged commit f2eff2a into delta-io:master Oct 15, 2026
43 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants