[
https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4251:
---------------------------------------
This is the setting I am thinking of, I believe we have root pg
credentials to create more databases. We have to check out the PG's operator, it may
have something there? Or should become a task in our operator somehow?
The default image supports declaring an admin user for remote access by explicitly
choosing an admin password. However like you say this would be new operator logic and
would require storage scaling and other updates to anything that's a shared
resource/setting (max connections?). It seems simpler for now to just have an instance
per vdb that has materialization.
I was meaning no security, as it is intracluster and trust the client
app. But trusting over the certificate is the correct way.
It's only intracluster if we don't add a pg route.
There are other considerations, such as by default if ssl is used over pg by default you
cannot make a non-ssl connection.
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)