[ 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. -- 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

[ https://jira.jboss.org/browse/TEIIDDES-452?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-452: ---------------------------------- Assignee: Barry LaFond Fix Version/s: 7.1 Affects Version/s: 7.1 -- 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

[ 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. -- 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