[teiid-issues] [JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-4629:
---------------------------------------

> Can you elaborate on concepts removed

A lot of the changes were just to bring things in line with master, which could have been just formatting.  Other changes were to pull out any of the client changes, embedded connection reconnect logic, and authorization.

> Let's handle this as separate JIRA.

I'm fine with that.  Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options.

Another small consideration is that source loading based upon ddl is serialized.  We may need to have access to native metadata spawn a job.

> Offer a ddl solution to replace the vdb.xml
> -------------------------------------------
>
>                 Key: TEIID-4629
>                 URL: https://issues.jboss.org/browse/TEIID-4629
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine, Server
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>             Fix For: 9.2
>
>
> Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl.  We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible.  Ideally this should support as much alter functionality as possible.



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