Related guide: resource-definition-validation.
Opened from Remediation proposals… on the Source validation results dialog (or by double-clicking an issue summary).
Layout
-
Issue header — short severity / kind / field / message context
-
Proposal summaries (top ~30%) — read-only table with one row per proposal summary
-
Selected proposal details (bottom ~70%) — full summary, type, and untruncated details text (wrap + scroll)
-
Footer — Apply proposal and Close always visible at the bottom of the dialog
Source schema drift (simple rules)
The catalog describes a source table. Validation may compare it to the live source. Remediation never changes the catalog.
| Proposal | What it does |
|---|---|
Expand field length in target models and database schemas (using the catalog) |
Reads the field length from the catalog, expands mapped model attributes, and writes a SQL workflow for target tables. Catalog is left alone. |
Note: live is longer/shorter than the catalog |
Informational. If the live length is the intended truth, update the catalog yourself in the Data Catalog, then re-validate. |
Physical DDL is not run when you apply. Run the generated workflow per environment when ready.
Configure the root folder under Configuration → Hopper EDW → Schema remediation folder.