[
https://issues.jboss.org/browse/TEIID-3480?page=com.atlassian.jira.plugin...
]
Kylin Soong edited comment on TEIID-3480 at 3/24/16 10:28 AM:
--------------------------------------------------------------
What's the difference caused by different position of status table:
* Internal Materialization use system table SYSADMIN.MatViews as system table
* External Materialization use a external table passed via
"teiid_rel:MATVIEW_STATUS_TABLE" parameter point to a external data store
server
But both CLI/web-console get data via "select * from SYSADMIN.MatViews", so in
External the return is raw data(the updated data saved in external server)
Now if close/remove difference, keep Internal and External consistent, there are lots of
logic related, the logic related with mat including: MaterializationManager, metadata
loading, query logic, so far, I have concern is why we need create a status table in
External? this not only increase the complexity, but also caused the inconsistent, if keep
external use SYSADMIN.MatViews as status table, it will be easy to solve this issue, any
ideas for this?
was (Author: kylin):
What's the difference caused by different position of status table:
* Internal Materialization use system table SYSADMIN.MatViews as system table
* External Materialization use a external table passed via
"teiid_rel:MATVIEW_STATUS_TABLE" parameter point to a external data store
server
But both CLI/web-console get data via "select * from SYSADMIN.MatViews", so in
External the return is raw data(the updated data saved in external server)
Now if close/remove difference, keep Internal and External consistent, there are lots of
logic related, the logic related with mat including: MaterializationManager, metadata
loading, query logic, so far, I have concern is why we need create a status table in
External? this not only increase the complexity, but also caused the inconsistent, if keep
external use SYSADMIN.MatViews as status table, it will be easy to solve this issue, any
ideas for this?
External Materialization status
-------------------------------
Key: TEIID-3480
URL:
https://issues.jboss.org/browse/TEIID-3480
Project: Teiid
Issue Type: Enhancement
Components: Server
Affects Versions: 8.4
Reporter: Ramesh Reddy
Assignee: Kylin Soong
Fix For: 9.0
When external materialization is configured with "STATUS" table, then Teiid
should expose those stats over CLI and in the web-console. Currently the internal
materialization does show status, need to expand to the external matviews.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)