Skip to content

Validate properties on load/upgrade instead of on read - #6648

Open
DomGarguilo wants to merge 2 commits into
apache:mainfrom
DomGarguilo:removeValidation
Open

DomGarguilo wants to merge 2 commits into
apache:mainfrom
DomGarguilo:removeValidation

Conversation

@DomGarguilo

Copy link
Copy Markdown
Member

Fixes #6634

Removes prop validation on read from SystemConfiguration, ResourceGroupConfiguration, and SiteConfiguration. Bad values no longer silently fall back to the parent value which matches how the other config classes already work.

Since reads no longer validate, resource group props are now validated on load and during upgrade which now matches how system, namespace and table props behave.

One behavior change is an invalid value that is in ZooKeeper is now used as-is instead of being replaced by the parent value.

@DomGarguilo DomGarguilo added this to the 4.0.0 milestone Nov 13, 2026
@DomGarguilo DomGarguilo self-assigned this Nov 13, 2026
@keith-turner

Copy link
Copy Markdown
Contributor

Was wondering if ZooBasedConfiguration.getParent() could be removed after these changes. Looked into and it seems like it may only be used by tests after the changes, so can not remove it.

This branch has not been deployed

No deployments
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.

Inconsistent and incorrect validation on property read

2 participants