Skip to content

[core] Defer file-store validation until runtime initialization - #10850

Open
zhoulii wants to merge 2 commits into
apache:masterfrom
zhoulii:fix/lazy-table-runtime-validation
Open

zhoulii wants to merge 2 commits into
apache:masterfrom
zhoulii:fix/lazy-table-runtime-validation

Conversation

@zhoulii

@zhoulii zhoulii commented Oct 28, 2026

Copy link
Copy Markdown
Member

Purpose

close #10849

Tests

@JingsongLi JingsongLi left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requirement fit: SUPPORTED. Implementation: FINDINGS (integration/test migration).

The upgrade-recovery scenario has concrete end-to-end value. I traced catalog loading, runtime initialization, cache publication, mutable options, serialization, and chain/fallback/auth wrappers. The actual SQL inspect -> reject invalid read/write -> repair -> read/write/drop flows pass locally on JDK 11: 7 Spark, 3 Flink filesystem/REST, and 2 Hive cases. Normal Maven verify, including formatting, Checkstyle, Enforcer and RAT, passed for those engine modules.

Core verification on JDK 8 ran 177 focused cases: 176 pass, but CatalogEnvironmentTest.testAppendTableUsesDependencyReadContext fails reproducibly at newRead() with "Data evolution config must enabled with row-tracking.enabled". The 28 new TableRuntimeValidationTest cases all pass. The inline finding also covers the related existing engine regressions visible in this head's CI; those failures need to be resolved before merging.

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.

[Feature] Defer file-store validation until runtime initialization

2 participants