Is there an existing issue for this?
Problem statement
the data contracts to dqx check generator should also generate schema validation checks based on what's defined in the ODCS data contracts
Proposed Solution
- Add a schema validation rule type: for each ODCS schema, generate one dataset-level rule that calls has_valid_schema with the expected schema derived from the contract (column names and Unity Catalog physicalTypes).
- Use strict mode only: exact column set, order, and types (no permissive/type-widening).
- Require every property to have Unity Catalog physicalType (e.g. STRING, INT, DECIMAL(10,2), ARRAY<STRING>). No ODCS→Unity mapping; missing or invalid physicalType raises an error.
- Make it opt-in by default: new parameter generate_schema_validation=True; set to False to skip these rules.
- Emit rules with user_metadata.rule_type: "schema_validation" and the expected DDL string so they can be filtered or reported separately.
Additional Context
No response
Is there an existing issue for this?
Problem statement
the data contracts to dqx check generator should also generate schema validation checks based on what's defined in the ODCS data contracts
Proposed Solution
Additional Context
No response