[
https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4251:
---------------------------------------
Issues with this approach:
- fail fast? the fdw seems to hang if the remote server is not available, but that
shouldn't really be a concern
- expanded transaction statement support. the fdw expects more syntax for start
transaction and abort transaction
- import seems to succeed and the tables are visible in pg_class, but they are not
resolvable
-- using create foreign table... does create a querable table - but of course is not what
I was going for
- the execution against a foreign table uses a different declare cursor syntax than we
currently have support for
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: 11.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)