[teiid-issues] [JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4526: ------------------------------------- I am trying to work/undestand from [~shawkins] comments from above - Thanks to [~kylin] looks like, based on 'refreshmatviewRows' procedure he already implemented the predicated based approach. - He also consolidated the loading and refreshing to same procedures calls for internal and external materialization. - I am not concerned about source not being transactional, as majority of sources Teiid uses for this feature are. The exception that really matters is JDG (although it is claimed to be transactional). We just need to document/recommend as such. - Lazy invalidation based on additional column needs a separate ticket. Not sure I understand the full benefits of this yet. - Also the consolidation of Status table management needs a separate ticket. This should be fairly narrow task. The second bullet is where the meat required for this JIRA IMO. We agree we need event handling. I first thought was to support event handling on views where they share the common primary key with the source table. Although that simple case, and PK might not match one on one with View's PK. This goes into comment about "manual" strategy where the predicate is anything into some what of "defined" predicate. We can design this to be pluggable or some kind rule based. [~shawkins] I do not think I understand the trigger semantics on source, can you explain further? I understand semantics, but I am failing to see responsibility? Are you saying these define a generic way to generate a event in the Teiid system, which could have originated from Debezium or otherwise. The actions you take in those triggers procedures can be update of the materialization table? -- This message was sent by Atlassian JIRA (v7.2.3#72005)