[
https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4251:
-------------------------------------
The second one is the thorniest issue. More than likely we'd need
to centralize the load logic.
We will have an Operator, which can be used to
coordinate events centrally. It does need to do the load logic, it just needs to elect a
member to delegate to. Is that something you can make use of with "existing
materialization" approach? as I gather fdw seems to be more work for not any improved
functionality.
Another option is since we are saying Teiid controls the PG instance, having a sidecar
kind of container to do the same co-ordination work?
Built in support for Postgres DB as materialization target
----------------------------------------------------------
Key: TEIID-4251
URL:
https://issues.jboss.org/browse/TEIID-4251
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.3
If Postgres database is available along with install or assumed that it is available,
then some of the materialization task can be automated, like
- Creation of a common STATUS table
- Creation of the materilization targets (create views on dbms)
- On load, on undeploy and load scripts for all the materialization views
We need to device a way this to be pluggable, such that based on success of this, we can
provide additional support for other sources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)