07-design-validation

To validate Gold layer design artifacts, you can cross-check YAML schemas against ERDs and lineage CSVs. This process identifies discrepancies in table definitions, column mappings, and foreign key references to prevent runtime bugs during the implementation phase.

Data lineage verification checks that every column defined in a YAML schema has a corresponding entry in the lineage CSV. This ensures full traceability of data transformations and confirms that all Gold layer mappings are accounted for before implementation.

Checking primary key and foreign key integrity involves validating that all foreign key references in your YAML schemas correctly point to existing primary keys in other tables. This prevents broken joins and referential integrity errors in your Gold layer.

Yes, you can cross-validate ERD diagrams against YAML schemas to ensure all tables and columns align perfectly. This catches discrepancies like a column existing in the ERD but missing from the YAML schema, ensuring strict design consistency.

Mandatory schema properties in Gold layer YAML files include required table definitions, column configurations, and primary key declarations. Checking these properties ensures all schemas adhere to required data governance standards before implementation handoff.

Gold layer schema validation fails on missing lineage entries when a column defined in the YAML schema lacks a corresponding mapping in the lineage CSV. Resolving this requires updating the lineage file to include all defined columns for complete traceability.