[teiid-issues] [JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13353676#comment-13353676 ] 

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.

> Add a ddl equivalent to the metadata tag
> ----------------------------------------
>
>                 Key: TEIID-4719
>                 URL: https://issues.jboss.org/browse/TEIID-4719
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>
> Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options.  In a zip deployment this will allow splitting the ddl over multiple files.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)