[teiid-issues] [JBoss JIRA] (TEIID-4807) DDL format of a vdb lacks import information

Steven Hawkins (JIRA) issues at jboss.org
Fri Mar 10 09:48:01 EST 2017


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

Steven Hawkins commented on TEIID-4807:
---------------------------------------

> This always been the case, we always returned the metadata, not import information.

But you are comparing apples to oranges.  In the old case the admin method was asking for the ddl specifically for a single schema.  In the new case you are returning the metadata for the entire vdb.  In the xml case you are returning a different set of metadata that the ddl case - that is not consistent. 

> What is missing? I am failing to understand that, can please explain?

The model element will still include all of the metadata tags, including "imports", and ddl - plus the additional full ddl.  That's not likely what the user would want.

> same here, I do not understand this.

There are two different usages being considered there.  One is informational - what is the schema contents for a given model.  The other is the conversion aspect.  It's the latter we we are not offering a 1-1 conversion.  We are offering ddl that does not reflect the deployment state of the vdb, but the runtime state.  That is functionally different until we only have a full online metadata system.

> DDL format of a vdb lacks import information
> --------------------------------------------
>
>                 Key: TEIID-4807
>                 URL: https://issues.jboss.org/browse/TEIID-4807
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.3, 9.2.1
>
>
> Database and schema imports are not represented from the admin getSchema logic.  It looks better that we still restrict this to just a schema for now.



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


More information about the teiid-issues mailing list