[
https://issues.jboss.org/browse/TEIID-5656?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5656:
---------------------------------------
Note that this is a mismatch between pattern and name. Since we don't specify or
capture what is the escape character is for the pattern we can't just say that the
name is the pattern.
DDL based import statement incorrectly parses the foreign schema
name
---------------------------------------------------------------------
Key: TEIID-5656
URL:
https://issues.jboss.org/browse/TEIID-5656
Project: Teiid
Issue Type: Bug
Components: VDB
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Major
Fix For: 12.1
The DDL import statement like
{code}
IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts
OPTIONS("importer.useFullSchemaName" 'false');
{code}
does not set the "importer.schemaPattern" to "public" instead it sets
to "importer.schemaName" property to "public" in runtime thus
invalidating its use.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)