[teiid-issues] [JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target
[
https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4251:
-------------------------------------
The biggest multi-tenet issue using the direct pg fdw integration is
the imported schema name limitation
fdw settings are not per pg database? or their
fdw settings are global? My only concern is the proliferation of a number of pg instances
in a given cluster. Maybe we can put in an assumption/limitation over the schema names and
find a way to warn or fail?
I agree that we start with the snapshot refresh, when we are ready to work with CDC we can
revisit choices available.
As per the connectivity from PG to Teiid, can it not be implicitly trusted over service?
if not yes a certificate based auth need to be devised. That may be useful in general with
any other jdbc/odbc client from the within the cluster.
Built in support for Postgres DB as materialization target
----------------------------------------------------------
Key: TEIID-4251
URL: https://issues.jboss.org/browse/TEIID-4251
Project: Teiid
Issue Type: Sub-task
Components: Server
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
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)