Data Lakehouse Schema Evolution Language Collocations
Practise the standard verbs for evolving a data lakehouse schema safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ every schema change in the lakehouse's catalogue so a downstream query never silently reads a column that no longer exists.'
We 'register a change' — the standard, established collocation for recording a schema update in a shared catalogue. The other options aren't the recognised term here.
2 / 5
Fill in: 'Adding a new column without a default value can ___ every historical row reading back as null once the query engine catches up.'
We say a missing default will 'leave' historical rows null — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the table schema alongside the data files so an old query can still read a partition written under a previous schema.'
We 'version a schema' — the standard, established collocation for tracking a table's structure changes over time. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a proposed schema change against downstream consumers before merging it, so a renamed column doesn't break another team's job silently.'
We 'validate' a change — the standard, simple collocation for confirming it won't break existing consumers. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ an old column gradually with a warning period instead of dropping it outright, so downstream jobs have time to migrate.'
We 'deprecate a column' — the standard, established collocation for phasing out a field with advance notice. The other options aren't the recognised term here.