[
https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2432:
---------------------------------------
reference
https://issues.jboss.org/browse/TEIID-2105 and the release note text is
"VDB.Status now has four states - LOADING, ACTIVE, FAILED, REMOVED. To check for
validity use the isValid method, rather than checking for the VALID state. FAILED
deployments will still be accessible via the admin getVDB methods."
removed should not be seen by the client, so that just leaves loading/active/failed. You
start as loading. You transition to active after all metadata has been loaded. This
means the vdb is complete and querable, but that you may get exceptions (isValid may be
false since a source may be down/missing). You transition to failed if there is a
non-recoverable exception during loading (typically a metadata validation issue).
Dynamic VDB isLoading state doesnt change on fail
-------------------------------------------------
Key: TEIID-2432
URL:
https://issues.jboss.org/browse/TEIID-2432
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 8.2
Reporter: Mark Drilling
Assignee: Ramesh Reddy
I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB
deployment is finished.
In my case the VDB dataSource is not available. I can see in the server log that the
deployment fails immediately, but the isLoading state remains true.
Is this in error, or what status should we be checking?
--
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