[teiid-issues] [JBoss JIRA] (TEIID-4121) Enhancing the External Materialization

[Kylin Soong (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243976#comment-13243976 ] 

Kylin Soong commented on TEIID-4121:
------------------------------------

A quick question, does the [1] ways still work, from MaterializationManager.java FinishDeployment(), seems this method will invoke SYSADMIN.loadMatView, and SYSADMIN.loadMatView depend on a *staging table*, a *status table* be created in physical source, but [1] not refer any of them, so my question:
# Does [1] docs works? refer to "your index creation may be more performant if deferred until after the table has been created", how to understand the 'index creation' and 'table has been created'? 
# Does Dsigner Tools designed external Mat View VDB works in DV 6.x?

[1] https://teiid.gitbooks.io/documents/content/caching/External_Materialization.html#_user_managed_materialization_management

> Enhancing the External Materialization
> --------------------------------------
>
>                 Key: TEIID-4121
>                 URL: https://issues.jboss.org/browse/TEIID-4121
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Query Engine
>    Affects Versions: 9.x
>            Reporter: Kylin Soong
>            Assignee: Kylin Soong
>             Fix For: 9.0
>
>
> The intention of move "status" table to physical database is to increase durable and fully control refresh and loading, but it increase the complexity.
> The "status" table by design should unique for whole VDB, if you look the https://teiid.gitbooks.io/documents/content/caching/External_Materialization.html#_usage_steps, the table structure:
> {code:sql}
> CREATE TABLE status
> (
>   VDBName varchar(50) not null,
>   VDBVersion integer not null,
>   SchemaName varchar(50) not null,
>   Name varchar(256) not null,
>   TargetSchemaName varchar(50),
>   TargetName varchar(256) not null,
>   Valid boolean not null,
>   LoadState varchar(25) not null,
>   Cardinality long,
>   Updated timestamp not null,
>   LoadNumber long not null,
>   PRIMARY KEY (VDBName, VDBVersion, SchemaName, Name)
> );
> {code}
> but currently, one VDB may have multiple "status" table, each view may have it's own "status" table. Further more, we can consider create status table automatically, which like internal, status create once VDB start, and configured in VDB scope.
> From finishedDeployment logic in MaterializationManager, MATERIALIZED_TABLE be used to determine whether the Mat is internal or external, But we lack the validation in metadata loading, in my previous test, the Internal Mat view configured lots of external view's properties like "status" table, the validation not throw excepton.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)