[teiid-issues] [JBoss JIRA] (TEIID-2057) Problem with dynamic VDB re-deploy when it contains a Virtual Model

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-2057:
-------------------------------------

- The problem with accessing the DDL is not during the deployment time, but once it is deployed. So, I am not sure how adding as archive helps. I agree this keeps the state as provided by the user. But for runtime state metadata is already fully available to the engine. However, we could add a method like "getSchema(vdbname, version, modelName) to the Admin API, that will return the DDL and internally during the parse time or after metadata load save the DDL to a separate file just as metadata cache file and supply to user when they requests through above method.

- yes, I see saving runtime errors as bad. Should differentiate between runtime and design/deploy time errors.

- All the methods on Admin API that operate on VDB take effect immediately. We do not provide any methods that modify the VDB and leave in state that requires a restart. So, I am not sure which methods you are mentioning that require a restart method.

- yes, addDataRole kind methods are used, since we do not have any tooling it is not wired anywhere currently. We did in 7.7 with Console plugin. 
                
> 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, Server
>    Affects Versions: 8.0
>            Reporter: Mark Drilling
>            Assignee: Ramesh Reddy
>             Fix For: 8.1
>
>
> 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