[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2584:
---------------------------------------
What are naming/versioning I should be concerned about?
The vdb name/version would need to be tracked as part of the table name (with some
consideration given to allowing the sharing of imported mat views).
Also we may need some kind of collection process that will delete invalid entries out of
the status table for vdbs that are missing/undeployed.
One thing I am struck is, how I could execute this non-blocking
manner?
Internally procedures are non-blocking - except when running in a transaction, such as
would be the case with an atomic block. In that case we are tied to serial processing.
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