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

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

> I thought nested transactions were not supported in Teiid procedure language, are they?

They could be but we don't consider them as currently supported.

> If you are saying two separate requests

I'm confused on what you mean by requests (user request?).  I'm saying that within the scope of a load procedure if you use a transaction specifically around the test for loading:

{code}
BEGIN 
...
declare boolean shouldLoad;
BEGIN ATOMIC
  update status set (isLoading = true) WHERE ... and isLoading = false;
  shouldLoad = (ROWCOUNT = 1);
END

if (shouldLoad)
...

END
{code}

Then regardless of the isolation level if shouldLoad is true, then you would proceed.  This of course glosses over any of the complexity with failed loads or initially populating a status entry.

As you are getting though if this is being run in the scope of a higher level transaction, then there will be an issue.

> but right now with this JIRA

No I think that is what you have to do.  Adding the consideration of implicit loading strategies is cumbersome.

> this enables Teiid to keep the cache near close to fresh

Not exactly - it provides a more centralized coordination mechanism and more easily allows for hard time based refreshing (refresh all at midnight, etc.).  However the real trick with freshness is based upon change events and 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
>             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