[teiid-issues] [JBoss JIRA] (TEIID-2057) Problem with dynamic VDB re-deploy when it contains a Virtual Model
[
https://issues.jboss.org/browse/TEIID-2057?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2057:
-------------------------------------
This is by design. There is no use for this text once the metadata is retrieved from it.
This will also reduce the foot print of the VDB. This is some discussion to add a admin
method given the VDB name and model name, Teiid can expose the metadata by exporting to
DDL.
Problem with dynamic VDB re-deploy when it contains a Virtual Model
-------------------------------------------------------------------
Key: TEIID-2057
URL: https://issues.jboss.org/browse/TEIID-2057
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 8.0
Reporter: Mark Drilling
Assignee: Ramesh Reddy
I am using the AdminAPI to add a View Model to a dynamic VDB. The initial deployment
succeeds - the VDB deploys and i can query the View.
However, then I retrieve the VDB via the Admin API. In debug, I can see on the view
model - that the schemaText field is now null. If I attempt to make other changes and
re-deploy, the re-deploy fails - the parser chokes on the null schemaText
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira