[teiid-issues] [JBoss JIRA] Commented: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-1470:
-------------------------------------

Should it try to retrieve metadata, or keep it as in_active based on metadata non-availability? If we try to retrieve, then it is a blocking operation for other processes. IMO, it should be in_active until user re-deploys the vdb, at which time the metadata is loaded.

> Deploying VDB XML file before data sources leads to failed deployment
> ---------------------------------------------------------------------
>
>                 Key: TEIID-1470
>                 URL: https://issues.jboss.org/browse/TEIID-1470
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 7.1.1
>            Reporter: Paul Nittel
>            Assignee: Steven Hawkins
>             Fix For: 7.4
>
>
> Using the dynamic portfolio example, the readme instructs the user to:
> Copy the following files to the <jboss.home>/server/default/deploy directory.
> 	- portfolio-vdb.xml
> 	- marketdata-file-ds.xml
> If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens.
> The VDB deploys (inactive state)
> The data source deploys successfully
> The VDB status changes to active.
> Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked.
> Issues at play are:
> 1) The readme's copying instructions are backwards, and
> 2) The VDB is marked as active when it should not be
> Both should be corrected.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira