[teiid-issues] [JBoss JIRA] (TEIID-2449) Allow for a vdb zip to store ddl outside of the vdb.xml

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Thu Mar 28 10:58:42 EDT 2013


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

Steven Hawkins commented on TEIID-2449:
---------------------------------------

The initial check-in adds VDBResource instances available via the MetadataFactory.getVDBResources for use by metadata repositories.  Another approach would be to make the resources available via the VDB, but that didn't seem appropriate given the remote usages.

A DDL-FILE repository was added that uses the metadata text to specify the location of the ddl file, which will be an absolute path relative to the root of the vdb zip.

The index logic was further refactored to remove unnecessary code, mostly related to update/save functionality and to remove the dependency on VirtualFile.  Also converted the IndexMetadataStore/IndexMetadataRepository into a single IndexMetadataRepository class.  This should address an issue where enterprise types from index vdbs are not be added into the metadatastore, since we were only setting the Schema.
                
> Allow for a vdb zip to store ddl outside of the vdb.xml
> -------------------------------------------------------
>
>                 Key: TEIID-2449
>                 URL: https://issues.jboss.org/browse/TEIID-2449
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Server
>            Reporter: Steven Hawkins
>             Fix For: 8.4
>
>
> Our current vdb.xml design will include the ddl metadata string in-memory which is not desirable for large metadata sets.  We should provide a built-in mechanism to relocate the metadata to separate files in a zip (which can also be a natural replacement for index files when the designer is ready).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the teiid-issues mailing list