[teiid-issues] [JBoss JIRA] (TEIID-2584) Add management features to materialization

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-2584:
-------------------------------------

Changed above check to 

{code:lang=SQL}
SELECT * FROM MAT_VIEW WHERE 1 = ALL(SELECT MVSTATUS(Valid, LoadState, OnErrorAction) 
FROM {statusTbl} WHERE VDBName=? AND VDBVersion=? AND SchemaName=? AND viewName = ?)
{code}

As I observed from previous check that EXISTS will be true for either valid or invalid situations as along there is a result, even if it is null. So, I choose the above kind of check, that seems work as expected.

Also implemented the "wait" action, when matview is not valid or not in "LOADED" state, the user query will wait until the "status" table is shows that the matview is in "LOADED" state with valid set to true. During the wait, the query submits polling commands to check the status of "status" table every 30 seconds. We could make this time-slot configurable if needed.
                
> Add management features to materialization
> ------------------------------------------
>
>                 Key: TEIID-2584
>                 URL: https://issues.jboss.org/browse/TEIID-2584
>             Project: Teiid
>          Issue Type: Feature Request
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>              Labels: Beta3
>             Fix For: 8.5
>
>
> Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. 
> External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira