[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=12797611#comment-12797611 ] 

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

>From the diff:

You could use a single system procedure with dynamic sql by passing in just the fully qualified name (probably in parts) and then use system lookups for the metadata.

Generally though there may be a performance hit from the atomic blocks as we'll be using an XA transaction rather than a local transaction, but there's not much we can currently do about that as the language/high-level processing does not know about connection management.

> I used "BEGIN ATOMIC" in procedure, but did not see intended effects in my testing.

I see at first you are selecting to test validatity with a transaction around the insert.  Is there a primary key or other constraint that would prevent two inserts?  Otherwise the txn block won't matter - but you may need to add exception handling to catch the pk violation.

Ideally you could use a merge statement in the place of the select/insert/update, but ours is currently too simplistic.



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