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

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-4626:
-------------------------------------

I think when to reload based on stale record count is thorny issue, this must be driven by the user. Whatever we do will not be sufficient for other user. How about user providing a procedure, which we can call with given statistics that tells us to start a reload or not?

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