Controlled casting coerces incoming values into types compatible with a target schema under explicit ingestion rules. It improves resilience when source data varies, but requires validation to prevent silent quality loss. section 6.1.3
Typical casting decisions include:
- Convert strings to timestamps when the target schema requires timestamp values. section 6.1.3
- Truncate decimals or insert nulls when incoming values cannot directly match the target type or field availability. section 6.1.3
- Combine casting with compatibility validation, while recognizing that tools differ in supported promotions and casting flexibility. section 6.1.3
Resilient ingestion
An ingestion pipeline can cast timestamp strings to the table’s timestamp type and insert nulls for missing fields, while retaining fail-fast checks for critical fields. section 6.1.3
