[teiid-issues] [JBoss JIRA] (TEIID-4131) External Materialized View's initial status should not insert into SYSADMIN.MatViews

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-4131.
-----------------------------------
    Fix Version/s:     (was: 9.x)
       Resolution: Rejected


The intent of this view is to show all materialized views - internal and external.  Since we locally maintain the state for the internal status it is shown here, but for performance and other considerations we don't show the external status.

> External Materialized View's initial status should not insert into SYSADMIN.MatViews
> ------------------------------------------------------------------------------------
>
>                 Key: TEIID-4131
>                 URL: https://issues.jboss.org/browse/TEIID-4131
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 9.x
>            Reporter: Kylin Soong
>            Assignee: Kylin Soong
>
> During VDB deploying, External Materialized View's initial status be insert into SYSADMIN.MatViews, this cause stale data, due to External Materialized View's status should go into physical database. Below is a example
> {code}
> SQL: SELECT VDBName, SchemaName, Name, TargetSchemaName, TargetName, Valid, LoadState, Updated, Cardinality FROM SYSADMIN.MatViews
> +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+
> |       VDBName        |    SchemaName    |         Name         | TargetSchemaName |           TargetName           | Valid  |   LoadState   | Updated | Cardinality |
> +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+
> | PortfolioMaterialize | pg_catalog       | matpg_datatype       | [NULL]           | #MAT_PG_CATALOG.MATPG_DATATYPE | false  | NEEDS_LOADING | [NULL]  |      [NULL] |
> | PortfolioMaterialize | pg_catalog       | pg_type              | [NULL]           | #MAT_PG_CATALOG.PG_TYPE        | false  | NEEDS_LOADING | [NULL]  |      [NULL] |
> | PortfolioMaterialize | StocksMatModel   | stockPricesMatView   | Accounts         | H2_STOCK_MAT                   | [NULL] | [NULL]        | [NULL]  |      [NULL] |
> | PortfolioMaterialize | StocksMatModel_1 | stockPricesMatView_1 | Accounts         | H2_STOCK_MAT_1                 | [NULL] | [NULL]        | [NULL]  |      [NULL] |
> | PortfolioMaterialize | StocksMatModel_2 | stockPricesMatView_2 | Accounts         | H2_STOCK_MAT_2                 | [NULL] | [NULL]        | [NULL]  |      [NULL] |
> | PortfolioMaterialize | StocksMatModel_3 | stockPricesMatView_3 | Accounts         | H2_STOCK_MAT_3                 | [NULL] | [NULL]        | [NULL]  |      [NULL] |
> | PortfolioMaterialize | SYS              | spatial_ref_sys      | [NULL]           | #MAT_SYS.SPATIAL_REF_SYS       | false  | NEEDS_LOADING | [NULL]  |      [NULL] |
> +----------------------+------------------+----------------------+------------------+--------------------------------+--------+---------------+---------+-------------+
> {code} 
> Note that stockPricesMatView, stockPricesMatView_1, stockPricesMatView_2, stockPricesMatView_3 should not go into SYSADMIN.MatViews



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