Table Of Contents
Table Of Contents

2024-05-13 - Rebuild all downstream tiles (admin feature)


Status: Available

Type: DataOps

Date: 2024-05-13


Historically when we updated a landing change rule for a history tile we needed to manually drop all the downstream tiles then rebuild them to pickup the change.

For example, if a user wanted to change the business key and or record effective date on the data contract, both those changes require all the tiles downstream to be rebuilt so the new keys and/or dates can flow through.


Admins now see an additional menu option on the load history which lets them trigger a complete rebuild of all downstream tiles.

This lets us quickly and safely propogate a history change through all layers.

Leverage the Magic

We leverage the existing blast radius and rollback load patterns to identify all affected tiles, then we drop the physical table which forces a rebuild the next time the pipeline is run. A rebuild is required because a change to the business key or business effectve date re-sequences all the records and may result in changes to the physical structure of the tables (ie partitions and clusters)

Last Refreshed

Doc Refreshed: 2024-05-20