Skip to content

handle edge case where batch fails but some tables succeeded - #4678

Closed
jgao54 wants to merge 1 commit into
dbi-501-allow-users-to-drop-columns-on-chfrom
edge-case-handling
Closed

handle edge case where batch fails but some tables succeeded#4678
jgao54 wants to merge 1 commit into
dbi-501-allow-users-to-drop-columns-on-chfrom
edge-case-handling

Conversation

@jgao54

@jgao54 jgao54 commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Handling an edge case for #4609. Scenario described here. The fix is to always process removed columns when normalize returns, whether it succeeds or fails. This is safe even if SetLastNormalizedBatchIDForTable flakes and normalize retries: the catalog would have the schema removed and subsequent normalize of the same table will succeed.

@jgao54
jgao54 requested a review from a team as a code owner August 7, 2026 22:36
@jgao54
jgao54 force-pushed the edge-case-handling branch 2 times, most recently from a044a43 to 1a1e758 Compare August 7, 2026 23:31
@jgao54
jgao54 force-pushed the edge-case-handling branch from 1a1e758 to f1f5ff2 Compare August 7, 2026 23:34
@jgao54
jgao54 requested a review from masterashu August 7, 2026 23:44
@jgao54 jgao54 closed this Aug 10, 2026
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.

1 participant