]
Mark Drilling resolved TEIIDDES-1927.
-------------------------------------
Resolution: Done
Found that "Execute VDB" action was not always causing a re-deploy. So in cases
where the translator was changed, etc, the 'old' VDB was getting re-used. Changed
so that the VDB always gets re-deployed if the Execute VDB action is used.
Need to test scenarios where vdb source translators are changed.
----------------------------------------------------------------
Key: TEIIDDES-1927
URL:
https://issues.jboss.org/browse/TEIIDDES-1927
Project: Teiid Designer
Issue Type: Task
Components: VDB & Execution
Affects Versions: 8.2
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.3
I encountered a couple confusing scenarios where I changed the translator on a vdb
source, but had no change on execution in designer. We need to test to ensure that vdb is
picking up translator changes as expected.
Scenario
- Import a source Model (in my case it was SF).
- Create a VDB and add the source model to it.
- Deploy VDB, execute query to verify can query ok.
- Change source translator in VDB to 'loopback'. Save VDB
- Redeploy VDB, then run query. Loopback was expected, but I still got SF data back
1) the scenario above changes the translator in the VDB, but there is still an annotation
in the source model with 'translator=salesforce'. So they are in conflict.
2) Changed the source model annotation translator to 'loopback', resync'd the
vdb, redeployed and queried again. Still got SF results instead of loopback. The
re-deployment is not picking up the translator change.
3) Finally, in the server view, manually 'un-deployed' the vdb. then went back
to model exployer and deployed again. Then I got loopback results.
--
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: