[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2584:
---------------------------------------
I took a pass through with some cleanups. The TriggerType is effectively the firing time.
Also we don't want to expose the view body through the trigger table. In theory it
would go on the sys.tables table (although there would be similar concerns about exposing
the logic publically) or on a sysadmin views table. The procedure sql was altered to not
directly need the transformation by using an option nocache on the view. The update
procedure was also modified - there's no need to prevent concurrent partial updates
(in theory you could try to detect when they are over lapping) and we don't want it to
alter the status of the materialization table if it fails - presumably there is no affect
on the current state as the operation should be rolled back. We may want to add another
status column or two to capture that a partial update has been performed and when, but
this should not be the same columns as the full load status.
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
Labels: Beta3
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