[
https://jira.jboss.org/browse/TEIID-1187?page=com.atlassian.jira.plugin.s...
]
Steve Hawkins resolved TEIID-1187.
----------------------------------
Resolution: Done
Also updated the docs. The only thing that seems like it may get people into trouble is
the non-versioned deployment scenario where we're allowing cache entries to still be
shared. We may need to have an option where an overwrite deployment purges cache and
kills all current connections or specifically scope the cache to the VDBMetaData object
(just like the materialized views).
Refine vdb version logic
------------------------
Key: TEIID-1187
URL:
https://jira.jboss.org/browse/TEIID-1187
Project: Teiid
Issue Type: Quality Risk
Components: Server
Affects Versions: 7.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1
We no longer have a built in configuration repository and we rely on container scans to
do deploys, so we have lost the ability to internally control the notion of a deployed vdb
version.
We should strive for the following:
1. Overwrite of a deployed vdb should not invalidate or otherwise corrupt current
connections.
2. Switching to a different vdb as the new default for a particular name should not
require two deployments of the same vdb.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira