SEEK-517: make catalog bootstrap concurrency-safe - #262
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughCatalog bootstrap now uses bounded retries, error classification, rollback, and metadata re-checks. SDK and namespace setup uses shared catalog table initialization. Tests cover missing tables, legacy indexes, concurrent creation, visibility failures, permissions, and invalid indexes. ChangesCatalog bootstrap
Estimated code review effort: 4 (Complex) | ~45 minutes Merge Risk: ⚪ Minimal · up to Catalog bootstrap now creates and verifies only missing schema objects, retries bounded transient DDL races, and shares this behavior with namespace catalogs. The supplied checks pass without an identified merge-blocking risk. Sequence Diagram(s)sequenceDiagram
participant BaseClient
participant CatalogDatabase
participant CatalogMetadata
BaseClient->>CatalogDatabase: Probe catalog table and index state
BaseClient->>CatalogDatabase: Create missing table or unique index
CatalogDatabase-->>CatalogMetadata: Expose updated catalog state
BaseClient->>CatalogMetadata: Re-read table and index visibility
BaseClient->>CatalogDatabase: Roll back transient failure
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
5af977c to
e88e9af
Compare
Summary
Verification
Source: SEEK-517
Summary by CodeRabbit