[teiid-designer-issues] [JBoss JIRA] Commented: (TEIIDDES-452) Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function.
[
https://jira.jboss.org/browse/TEIIDDES-452?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIIDDES-452:
--------------------------------------
One possible envisioning of solution:
a)Within tooling, user identifies view (let's call it “MyInfo”) for materialization
and chooses menu option to enable materialization.
b)Tooling generates a new physical/source model corresponding to the MyInfo model User
will have to select from limited set of supported target VDBs so appropriate types, etc.,
are used.
c)DDL scripts for the source schema that were previously generated at deployment would be
generated at this time and held as model project artifacts. These scripts could then be
executed against the target data source through a Data Tools connection to create the
target schema.
d)The new source model is bound to the original MyInfo model through a specialized
transformation. Thus MyInfo would have two “alternate” source transformations.
e)Based on a view property (Materialized?), queries against the view would be routed to
the materialization source model rather than through the primary data source(s).
f)This property should be override-able at runtime both through query directive (e.g.
Option nocache) and through administrative API/management console.
g)Refresh of materialized data is controlled by external process through execution of
external scripts that select from source an insert into materialization target or that
invoke virtual procedures that do the same. Invocation of scripts/procedures can be
scheduled through JON.
h)Custom logic can be incorporated into the refresh process for pre and post-processing
steps for truncate, load, swap and the entire refresh.
Fundamental rework of existing MetaMatrix materialization will become
mainly a Designer function.
-------------------------------------------------------------------------------------------------
Key: TEIIDDES-452
URL: https://jira.jboss.org/browse/TEIIDDES-452
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Van Halbert
Fundamental rework of existing MetaMatrix materialized views functionality to make mat
views first class objects in the system.
The changes for this feature include:
1.Moving away from the automagic creation of materialized view source/physical model and
ddl scripts upon VDB deployment
2.Making mat view source/physical models explictly modeled objects in Designer tooling.
3.Support external scripts to pull data from live sources and populate mat views.
4.Support virtual procedure logic to pull data from live sources and populate mat views.
This will required DDL execution capabilities such that virtual procedures can perform the
swap of staged data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira