[teiid-issues] [JBoss JIRA] (TEIID-5657) VDB Migration Tool

[Van Halbert (Jira)]

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

Van Halbert edited comment on TEIID-5657 at 2/19/19 2:56 PM:
-------------------------------------------------------------

The description indicates  a jar is created, just doesn't mention which jar.  Also, I can't find  a migrate jar or a repo of such.  Where can I find the jar?


was (Author: van.halbert):
The description indicates  a jar is created, just doesn't mention which jar.  Also, I don't a migrate jar or a repo of such.  Where can I find the jar?

> VDB Migration Tool
> ------------------
>
>                 Key: TEIID-5657
>                 URL: https://issues.jboss.org/browse/TEIID-5657
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Documentation, Quick Starts, Tooling
>    Affects Versions: 12.x
>            Reporter: Van Halbert
>            Assignee: Ramesh Reddy
>            Priority: Major
>
> A migration tool will be provided to convert customer vdbs into just ddl. More than likely this will be just a single ddl file - which will probably not be acceptable to customers with large vdbs.
> We have this utility already available as just a main method in one of our jars. It is anticipated that a maven repo will be distribution mechanism and minimal documentation will be provided.
> There should be optional validation available for the vdb ddl at build time. This breaks down into 3 parts:
> 1. static syntactic validation, potentially even fully resolving if all metadata is present. This makes sure that basic typos will be caught.
> 2. providing hard errors for things that are completely removed - an error for usage of soap or function models for example.
> 3. providing errors or warning for features that are not yet available - vdb imports, sources that aren't yet supported etc.
> To avoid introducing a new plugin or plugging into fmp it's been suggested that the validation could be run via a generated unit test, which ties into another task which is booster, base project, or last resort an arche type that scaffolds the developer project.
> This could possibly be included in the quickstarts as a means to facilitate its use.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)