I think when to reload based on stale record count is thorny issue, this must be driven by the user.

Add a full snapshot refresh strategy based upon table modifications ------------------------------------------------------------------- Key: TEIID-4626 URL: https://issues.jboss.org/browse/TEIID-4626 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 9.3 using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source.