jayeshchoudhary opened a new pull request, #17462:
URL: https://github.com/apache/pinot/pull/17462
We are building UI flows that need to validate specific parts of table
configuration
independently, without running all validations. For example:
1. **Schema validation flow**: Validate only schema and related ingestion
configs
(transformConfigs) without validating indexing, upsert, or task configs
2. **Partial config updates**: When updating only indexing configs, skip
expensive
validations for unchanged parts
3. **Iterative development**: Allow developers to validate one section at a
time
during table config creation
Currently, the table config validation API is all-or-nothing - it validates
everything
or fails. This makes it difficult to:
- Provide targeted validation feedback in UIs
- Validate draft configurations that are incomplete
- Speed up validation by skipping irrelevant checks
## What
Added two query parameters to validation APIs:
- `validationTypesToSkip`: Skip specific validation types (e.g.,
`?validationTypesToSkip=TASK,UPSERT`)
- `validationTypesToValidateOnly`: Validate only specific types (e.g.,
`?validationTypesToValidateOnly=SCHEMA,INGESTION`)
Supported validation types:
- SCHEMA - Schema name matching and validation
- INGESTION - Transform, filter, and aggregation configs
- INDEXING - Index configurations (star-tree, inverted, etc.)
- TIER - Tier configurations
- RETENTION - Retention and validation configs
- UPSERT - Upsert and dedup configurations
- TASK - Task configurations
- INSTANCE_ASSIGNMENT - Instance pool and replica group configs
- ALL - Special keyword for all validations
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
