Ultimate access to all questions.
A table named customer_churn_params
in the Lakehouse is utilized for churn prediction by the machine learning team. This table contains customer information aggregated from multiple upstream sources. Currently, the data engineering team refreshes this table nightly by completely overwriting it with the latest valid values from upstream sources.
The ML team's churn prediction model is stable in production, and they only need to generate predictions for records that have been modified within the last 24 hours.
What approach would streamline the process of identifying these recently changed records?