[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment
[
https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1470.
-----------------------------------
Resolution: Done
Updated the status checking code to relaunch the metadata load asynchronously if needed.
This means that if a datasource has yet to be deployed, its deployment will trigger the
metadata load.
If a datasource has been deployed, but there is an error during the metadata load (db
unavailable, etc.) then the vdb will be in an invalid state. just as with the previous
case, redeploying the datasource will trigger the metadata load.
There is no code yet for automatic retry/polling against a source that is available, but
there is an error during load.
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