[
https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-4526:
------------------------------------
To create bullet points related to the challenges to making this work:
* Since we allow for hand editing and only capture a simple quoted name in source, we
first have a matching problem from any event source to our source metadata.
* There can be type issues or even the consideration for masking or other effects.
Inferring values directly from the change event can be an issue as the CDC layer is
broadcasting raw values, not what you would fetch over jdbc.
* Aggregates may need to be recomputed, multiple rows removed, etc.
Thoughts on implementation:
* Keeping some notion of how "dirty" a particular materialized view is (number
of updates that affect the view vs. number of view rows) and trigger a full refresh above
a given threshold.
* Need to determine if there are differing expectations for internal vs. external
materialization.
Integrate with Debezium for CDC for maintaining materialized views
------------------------------------------------------------------
Key: TEIID-4526
URL:
https://issues.jboss.org/browse/TEIID-4526
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 9.2
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Critical
Integrate with Debezium so that Teiid will be able to consume and react to the row-level
change events and do something interesting with them, such as update the materialized
view(s).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)