4 - Exercise Summary

✅ What you built

A primary key data expectation check on your flight_alerts_clean dataset.

✅ What you learned

1. The transforms-expectations library must be imported into your repository before it can be referenced. It may be there by default.
2. You can set the on_error value to FAIL or WARN depending on whether you want to abort the job or simply notify of the failure respectively.
3. When you add an expectation, your repository’s Build helper adds an Expectations tab for viewing the results of the check.
4. Coded expectations show up in the Data Health application as Data Expectations Monitor.
5. Unlike health checks you create, you are not automatically subscribed to data expectations. You must choose Watch from the Data Health app.