8:21 p.m.
Ramesh Reddy created TEIID-2021:
-----------------------------------
Summary: Fail the VDB deployment when translator is not available
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:31 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-2021.
---------------------------------
Resolution: Done
Added check to VDB deployer to validate translator's existence.
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2021:
---------------------------------------
Shouldn't there have been a startexception from VDBService.createConnectorManagers?
Also don't we want the deployment to succeed so that the vdb can activate itself it
the required translators are added?
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2021:
-------------------------------------
Once the service starts, the deployment would have been finished. So, even throwing the
StartException the user need to undeploy and re-deploy the VDB. By stopping at deployment,
the undeploy is not required.
The code always assumed that the translators were already been deployed, so that we can
associate connector managers at VDBService start with vdb service. Treating them as data
sources, where they are loosely coupled can be done, but that needs to more work.
Currently when a translator is removed, the vdbs that depend on it stopped, and once they
are available then the service starts again.
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:03 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2021:
---------------------------------------
Isn't the last statement exactly what we're talking about - "Currently when a
translator is removed, the vdbs that depend on it stopped, and once they are available
then the service starts again." If it's valid to be deployed and then have a
translator removed, then it should be valid the other way around too.
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2021:
-------------------------------------
yes, with change to make them service dependency to start with; but need to put in a model
error to expose the error, I will re-open jira to do that instead. If you want you defer
it to 8.1
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Ramesh Reddy reopened TEIID-2021:
---------------------------------
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:19 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2021:
----------------------------------
Fix Version/s: 8.1
(was: 8.0)
Pushing to 8.1. For 8.0 users will need to deploy all needed translators before deploying
vdbs.
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:04 a.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-2021.
---------------------------------
Resolution: Done
Removing the hard depolyment time requirement to have translators deployed prior to VDB
deployed. In this situation, the system will log a error message to console and as well as
VDB errors area. The VDB will be deployed but the VDB service will not be started until
the translator is available.
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:42 p.m.
[
https://issues.jboss.org/browse/TEIID-2021?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-2021.
---------------------------------
Fail the VDB deployment when translator is not available
--------------------------------------------------------
Key: TEIID-2021
URL: https://issues.jboss.org/browse/TEIID-2021
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
VDBDeployer checks for the override translator types, however it does not check for the
base translators that are configured in the VDB. So, when a VDB with unknown translator is
deployed, it gets deployed but never exposes any error information as to why the VDB is
not "active".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4322
days inactive
4428
days old
9 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Steven Hawkins (JIRA)