[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:all-tabpanel ]

Kylin Soong updated TEIID-4121:
-------------------------------
    Description: 
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, but current one VDB may have multiple "status" table, each view may have a "status" table.
Further more, we can consider create status table automatically, which like internal, status create once VDB start, and configured in VDB scope.


  was:
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, but current one VDB may have multiple "status" table, each view may have a "status" table 


        Summary: Enhancing the External Materialization  (was: Enhancing the Teiid Materialization)


> 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: Steven Hawkins
>             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, but current one VDB may have multiple "status" table, each view may have a "status" table.
> Further more, we can consider create status table automatically, which like internal, status create once VDB start, and configured in VDB scope.



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