[ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin... ] Ramesh Reddy edited comment on TEIID-4719 at 1/25/17 8:14 PM: -------------------------------------------------------------- Actually the current import syntax looks like {code} IMPORT FOREIGN SCHEMA remote_schema [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ] FROM SERVER server_name INTO local_schema [ OPTIONS ( option 'value' [, ... ] ) ] {code} So to adopt this, how about {code} IMPORT FOREIGN SCHEMA remote_schema [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ] FROM REPOSITORY {repo} INTO local_schema [ OPTIONS ( option 'value' [, ... ] ) ] {code} OPTIONS would need to have the \{arg\} depending upon the \{repo\} type. was (Author: rareddy): Actually the current import syntax looks like {code} IMPORT FOREIGN SCHEMA remote_schema [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ] FROM SERVER server_name INTO local_schema [ OPTIONS ( option 'value' [, ... ] ) ] {code} So to adopt this it will be {code} IMPORT SCHEMA remote_schema [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ] FROM {repo} INTO local_schema [ OPTIONS ( option 'value' [, ... ] ) ] {code} OPTIONS would need to have the \{arg\} depending upon the \{repo\} type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)