[
https://issues.jboss.org/browse/TEIID-4121?page=com.atlassian.jira.plugin...
]
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
was:After some investigation
Enhancing the Teiid 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
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)