[
https://issues.jboss.org/browse/TEIID-5850?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5850:
---------------------------------------
So the proposal here is to:
1. Don't require CREATE FOREIGN DATA WRAPPER salesforce - by a vendor like pg that
creates a dummy fdw. Instead we should just skip directly to:
CREATE FOREIGN DATA WRAPPER mysalesforce TYPE salesforce ...
We can consider using the term HANDLER in addition to or instead of TYPE here. That
somewhat aligns with pg.
2. Better document what properties are supported when - only resource-name on create
server, and no properties if you create a "dummy" fdw.
DDL server and foreign data wrapper handling is unclear
-------------------------------------------------------
Key: TEIID-5850
URL:
https://issues.jboss.org/browse/TEIID-5850
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 13.0, 12.2.2, 12.3.1
Original Estimate: 6 hours
Remaining Estimate: 6 hours
CREATE server statements in DDL are effectively ignored in the conversion to runtime
state - they are simply validated. Similarly a CREATE foreign data wrapper statement that
does not specify a type is ignored.
Attempting to do something like:
{code}
CREATE FOREIGN DATA WRAPPER salesforce;
CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS
("resource-name" 'salesforce', supportsOrderBy true);
{code}
or
{code}
CREATE FOREIGN DATA WRAPPER salesforce OPTIONS (supportsOrderBy true);
CREATE SERVER salesforce FOREIGN DATA WRAPPER salesforce OPTIONS
("resource-name" 'salesforce');
{code}
will not result in supportsOrderBy being set on the translator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)