DEPENDENCY-ORDERED DELIVERYRelease Control
A safe migration sequence with explicit owners, validation gates, and rollback preserved until cutover.
parallel_typed_field
HIGHEVIDENCE CONFIDENCEReady for coordinated review
Technical fix drafts are available. Dynamic SQL and regional approvals remain open.
Lineage tracedFix drafts readyOwner approvals
01Proposed safe rollout
Introduce a parallel typed field for `customer_id`, validate the safe cast from `varchar` to `bigint`, and migrate downstream consumers in stages.
4 STAGES
- 01
PREPAREAdd a parallel typed field for `customer_id` alongside the current `varchar` contract.Keep the original contract available and make rollback immediate.
READY
- 02
MIGRATEBackfill the parallel field with a safe cast from `varchar` to `bigint` and record validation results.Move consumers in observed dependency order and monitor regional impact.
PLANNED
- 03
MIGRATEMigrate observed downstream assets to the new typed field in hop order after owner review.Move consumers in observed dependency order and monitor regional impact.
PLANNED
- 04
CUTOVERPromote the new typed field only after compile, test, and backfill validation succeed for `bigint`.Complete only after owners and validation gates pass.
PLANNED
Publish decisionPut the plan where data teams work.
Draft the incident, critical tags, and migration notes back into DataHub.
Review DataHub actions →
TAKE IT WITH YOUDownload all results
Choose a ready-to-share text or PDF export for the full bundle or any individual result.
Impact reportComplete evidence
TXTPDF
Discovery querySQL Server read-only scan
TXTPDF
Proposed fixesReviewable SQL drafts
TXTPDF
Validation queriesConversion and null checks
TXTPDF
Rollback runbookOwner-gated recovery steps
TXTPDF
SARIF resultsCI-compatible findings
TXTPDF