[
https://issues.jboss.org/browse/TEIIDDES-2861?page=com.atlassian.jira.plu...
]
Barry LaFond resolved TEIIDDES-2861.
------------------------------------
Resolution: Rejected
[~van.halbert] There is a problem with importing dynamic VDB containing extension
properties because it won't contain extension namespaces like you'd have when
defining a complete DDL model definition. In addition, there's no way to determine
the actual datatype of any of the extension values.
Confusion around DDL file and "ddl in -vdb.xml" is covered in earlier comment
Import DDL option is confusing
------------------------------
Key: TEIIDDES-2861
URL:
https://issues.jboss.org/browse/TEIIDDES-2861
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 10.0.1
Reporter: Van Halbert
Attachments: jdg-remote-cache-mat-vdb.xml, portfolio-vdb.xml
Have the following comments when trying to use the DDL importer to import a dynamic vdb:
- It refers to everything as DDL, when dynamic vdb is not
- the file chooser defaults to DDL, when maybe it should have an option for .xml
- on the importer, there's a Mode type. When importing dynamic VDB's, this
shouldn't apply, because the dynamic vdb can have both virtual and source models.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)