[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2584:
---------------------------------------
Some questions/thoughts:
create a "load" procedure like
Do you mean you want to write this as a system procedure? I think that could work, but it
wouldn't currently give you control of connections. At the least you'd want to
use BEGIN ATOMIC
Are you envisioning a status table on each source per vdb, or a single status table for
all of teiid? Each has considerations for table/entry naming/versioning.
Are you suggesting that the scripts execute as dynamic sql or against the source native
procedure?
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