[teiid-issues] [JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13369237#comment-13369237 ] 

Steven Hawkins commented on TEIID-4626:
---------------------------------------

Observations:

Incoming objects can contain procedures and views as well.  You would need to recursively navigate to discover all source tables - but you just want a unique set.

Since the triggers can now show up in exported ddl, we may want some way of excluding them.

The trigger name is not guaranteed to be unique - but it is highly likely given the naming convention.

Alter view would require the triggers to be dropped/readded, but we can also just document that as a limitation.

> 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)