[
https://issues.jboss.org/browse/TEIID-5850?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5850.
-----------------------------------
Fix Version/s: (was: 12.2.2)
(was: 12.3.1)
Resolution: Done
Since there was some documentation on the override, this is not as critical as it
initially seemed. However we should not require dummy create foreign data wrapper
statements, so the code is now tolerant to that. Docs have been updated to reflect this.
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
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)