[JBoss JIRA] (TEIID-2445) vdb.xml usability enhancements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2445?page=com.atlassian.jira.plugin... ]
Work on TEIID-2445 started by Steven Hawkins.
> vdb.xml usability enhancements
> ------------------------------
>
> Key: TEIID-2445
> URL: https://issues.jboss.org/browse/TEIID-2445
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
>
> Couple of usability enhancements need to be done on the -vdb.xml to make the intent clear
> UseConnectorMetadata=true/cached
> - The true case could be removed entirely. The notion of metadata caching could be handled by a model property and should probably be more baked into the MetadataRepository facility (such as passing the cached metadata in for update).
> supports-multi-source-bindings=true/false
> - Since we have mostly removed the binding terminology, it would make more sense to call this just multi-source or multisource (which is consistent with the multisource.columnName and addColumn properties). We could also automatically infer it to be true when there are multiple sources listed for a single model (which is currently an error case without this property) so that it would only be needed if you wanted a single source to appear as if it were a multisource model.
--
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
11 years, 9 months
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2432:
---------------------------------------
> We need some quick way to represent a recoverable error, rather than user looking at model errors.
I know that is the goal, but I don't think you understood me. VDB loading and model metadata failed means it is a recoverable error. I'm just trying to keep the states to a minimum. There's no problem though with adding another state.
> 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
11 years, 9 months
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Mark Drilling commented on TEIID-2432:
--------------------------------------
Yes, that last statement summarizes it - I think the states should indicate somehow if its recoverable. I understand the current mechanism now, but I think this could be a source of confusion for users in the future.
> 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
11 years, 9 months
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2432:
-------------------------------------
IMO, I do think we need two states, because from earlier discussions
He was not sure if the VDB was deployed first vs the data source deployed first. We did not wanted to create that dependency in deployment chain. Even if both configuration went at same time, or one after the other in right dependency timeline, since AS7 deployment process being asynchronous we could not depend on, when one is finished, so that other can start. Thus one of the reason we had the data source not availability as soft error. If we make that as hard error as single state "FAILED", then there may be some false deployment errors.
We need some quick way to represent a recoverable error, rather than user looking at model errors.
> 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
11 years, 9 months
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2432:
---------------------------------------
In the context of a metadata load WAITING is just a special case of FAILED, such that the overall deployment is still loading. However we can treat that as two states if a single seems too complicated.
> 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
11 years, 9 months
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2432:
-------------------------------------
I do not think that will still not solve his problem, as it is WAITING state. We need to break down the LOADING state. He needs a way to represent a DATA-SRC-ERROR with out actually looking into error messages on model.
> 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
11 years, 9 months
[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2432:
---------------------------------------
So Mark how would a Model.getMetadataStatus where the Status could be one of (LOADING, LOADED, or FAILED) work?
> 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
11 years, 9 months