[
https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4251:
-------------------------------------
It will need to fully babysit that load - if the delegated pod goes
down, then the load needs to be restarted.
Yes, it can effectively do that, it can keep checking for status and if failed it can
resubmit the request.
Both have a very weak notion of periodic invalidation
I
thought they were based on the status table times, if yes, Operator can only issue on
correct time invalidations. Basically Operator reconciler is tick at specified intervel,
what you want to do it upto you.
We really do not need coordination among nodes as if you use cental PG store right? that
would leave service account concerns and DDL generation concerns.
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)