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

[Steven Hawkins (JIRA)]

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

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

Looking good.  A couple of thoughts and questions:

I think we'll want to introduce a new system table to expose the transformation sql rather than through the properties table.  We can use a sysadmin table as to not expose inadvertently expose transformation logic that may be intended to be more private and we can ensure that we aren't colliding with any existing property key.

With the load procedure shouldn't we return a negative status code to indicate loading/loaded rather than 0?

Should there be exception handling for inserting a status entry?  Alternatively could this be done at vdb startup time?

How would a long load or an unexpectedly failed load be handled - in the former case it seems like it's possible to have concurrent loads and in the latter it seems like some manual process would be needed to clear the loading status.

Should the start/shutdown hooks also be definable via the vdb.xml?

>From above #5 - How does this work in a cluster?

What tie-ins are you thinking of exposing for incremental updates? 
                
> 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