[
https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4626:
---------------------------------------
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?
I'm not sure I follow this in the context of this issue - are you talking about
implementing row level lazy updates? For this issue we're not assuming row level
tracability and simply tracking any update as a modification.
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)