Skip to content

Skip partition pruning for manifests whose spec references a dropped source column#2845

Open
anoopj wants to merge 2 commits into
apache:mainfrom
anoopj:fix-scan-dropped-partition-source
Open

Skip partition pruning for manifests whose spec references a dropped source column#2845
anoopj wants to merge 2 commits into
apache:mainfrom
anoopj:fix-scan-dropped-partition-source

Conversation

@anoopj

@anoopj anoopj commented Jul 18, 2026

Copy link
Copy Markdown
Member

Which issue does this PR close?

Closes #2844.

What changes are included in this PR?

When a scan has a predicate, planning resolves every manifest's spec partition type against the snapshot schema. Manifests written under a historical spec whose source column was later dropped (which is a legit possibility in v2+) fail that resolution, so one such manifest fails the whole scan, even when the predicate only references live columns.

This PR is the stopgap described in #2844. The longer-term fix is deriving partition types from transforms where possible (as iceberg-java does in apache/iceberg#17262), which would also restore pruning on a historical spec's still-live partition fields.

Are these changes tested?

yes. added tests

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.

Filtered scans fail entirely for tables where a historical partition spec's source column has been dropped

1 participant