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

Tue Aug 27 15:22:26 EDT 2013

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

Steven Hawkins commented on TEIID-2584:
---------------------------------------

Can we also remove or change the property form of MATERIALIZED_TABLE (which can be determined from the materialized_views table) and the UPDATE_COUNT?  The fewer "med" properties we natively rely on the better.

For the triggers table, see the system tables in oracle/pg.  You'd likely have columns:

schema, table, trigger body, trigger type (INSTEAD OF), triggering event (INSERT/UPDATE/DELETE), status (ENABLED/DISABLED)

common stuff - which we currently don't track as we aren't creating a proper metadata record:

name, description, uid

Yes, the refresh procedure looks about right (With an atomic block and dynamic sql for the delete/select that should do the trick).  We should allow a variation of that to work against internal materialized views as well.  We can leave off manipulations to the cache hint then.

Another open issue seems to be that the engine does not have a built-in way to react to the mat view status.  If the status is something other than loaded/valid, then we should likely have a configurable outcome - ignore, error, wait?, refesh?, etc.

> 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