[teiid-designer-issues] [JBoss JIRA] Resolved: (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...
]
Barry LaFond resolved TEIIDDES-452.
-----------------------------------
Resolution: Done
1) Added "materializedTable" reference to relational metamodel for Table,
BaseTable and View.
2) Added "Modeling > Create Materialized Tables" action to context menu when
selecting one or more Views or Tables
3) Allows user to select (or create) a Target Relational model for the
"materialized" tables to persist.
4) After creation of materialized table, the "reference" to it is set on the
"virtual" table/view
5) A model dependency is created (model import) between the view and source models
6) Indexing the "view" model will now result in the appropriate
"materializedTableID" being set (This was done previously during VDB.save())
7) When Virtual model is added to a VDB, the dependency is detected and the
"Materialized" relational model is added as well (including index file)
Note that "Materialized" metamodel type is NOT used anymore.
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
Affects Versions: 7.1
Reporter: Van Halbert
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.1
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