Skip to content

fix(catalog): reject invalid current metadata version before staging - #1719

Open
fallintoplace wants to merge 5 commits into
apache:mainfrom
fallintoplace:fix/catalog-invalid-metadata-version
Open

fix(catalog): reject invalid current metadata version before staging#1719
fallintoplace wants to merge 5 commits into
apache:mainfrom
fallintoplace:fix/catalog-invalid-metadata-version

Conversation

@fallintoplace

@fallintoplace fallintoplace commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

What changed

  • Reject invalid current metadata locations before staging updates.
  • Keep legacy vN.metadata.json and vN.gz.metadata.json locations working.
  • Use version 0 for creates and reject empty locations for existing tables.

Why

A failed metadata filename parse used to become version 0 through -1 + 1. That could hide malformed catalog state and stage the next update at the wrong version.

Tests

  • go test ./catalog/internal -count=1
  • go test ./... -count=1

@fallintoplace
fallintoplace force-pushed the fix/catalog-invalid-metadata-version branch from 8a71b29 to ae002d3 Compare August 8, 2026 23:06
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