]
Steven Hawkins resolved TEIID-4388.
-----------------------------------
Resolution: Rejected
This is expected behavior. I'm not sure exactly what would make sense from a
enhancement perspective. It would be a new timeout and would simply change the status to
failed, however you can already see the reason while it's still loading with the model
status. So maybe this is more of UI issue or a new state name, such as loading-retry.
If model fails to load native metadata, VDB has still status LOADING
--------------------------------------------------------------------
Key: TEIID-4388
URL:
https://issues.jboss.org/browse/TEIID-4388
Project: Teiid
Issue Type: Bug
Affects Versions: 8.12.5
Reporter: Juraj DurĂ¡ni
Assignee: Steven Hawkins
If one model fails to load native metadata, VDB's status is still LOADING.
{code:plain|title=CLI status}
[standalone@localhost:9999 /] /subsystem=teiid:get-vdb(vdb-name=test,vdb-version=1)
{
"outcome" => "success",
"result" => {
"vdb-name" => "test",
"status" => "LOADING",
"vdb-version" => 1,
...
"models" => [
{
"model-name" => "Source1",
...
"metadata-status" => "LOADED"
},
{
"model-name" => "Source2",
...
"validity-errors" => [
{
"severity" => "INFO",
"message" => "TEIID50029 VDB test.1 model
\"Source2\" metadata is currently being loaded. Start Time: 8/17/16 7:41
AM"
},
{
"severity" => "ERROR",
"message" => "TEIID31178 Could not obtain
connection for schema Source2, but one is required for metadata load. "
}
],
...
"metadata-status" => "FAILED"
},
{
"model-name" => "Source3",
...
"metadata-status" => "LOADED"
}
]
}
}
{code}