[
https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4626:
-------------------------------------
Yes, RefreshType is not required on {{Status}} table, I realized that after the comment.
Yes, on EAGER right now it is updating the view for each event, my comment was more
specific to *if* we ever need to do anything on TTL, but since the view always up to date,
there is nothing to be done.
On the "LAZY" case, I see that in update/delete case setting value to -1 works,
but I am not sure how to handle a "insert" case? any suggestions? As per the
full update of all invalid rows collected over the time, I am sure we can develop further
refinements/additions to TTL strategy.
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)