[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2584:
-------------------------------------
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.
Two questions on this (the reason why I went current route)
1) Currently both SYS and SYSADMIN are both categorized as "SOURCE" schemas,
should I add another at "VIRTUAL" schema for this purpose?
2) How can I look up metadata inside the virtual procedure?
To execute as system procedure in SYSADMIN, I could not fold all the needed statements
like truncate/load/swap into single statement.
I will rewrite using "merge". Also, since these are async loads I was not
concerned about the performance hit.
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