[teiid-issues] [JBoss JIRA] (TEIID-1917) Teiid VDB Previous Version not accessible

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-1917.
-----------------------------------

        Labels: VDB Version  (was: Issue VDB Version)
    Resolution: Rejected


Versioned deployments are working as expected.  

Gautam, that is a valid name for a dynamic vdb deployment, but typically dynamic vdbs are not versioned deployments. Previous versions remain until specifically removed.  And yes, if there are active connections to a removed vdb it will remain available to those sessions.  On a non-versioned deployment which overwrites an existing vdb, the previous sessions are terminated.
                
> Teiid VDB Previous Version not accessible
> -----------------------------------------
>
>                 Key: TEIID-1917
>                 URL: https://issues.jboss.org/browse/TEIID-1917
>             Project: Teiid
>          Issue Type: Bug
>          Components: AdminApi
>    Affects Versions: 7.6
>            Reporter: Gautam Banerjee
>            Assignee: Steven Hawkins
>              Labels: VDB, Version
>
> There can be multiple VDBs of different versions deployed and we can connect to a specific version (documentation says that). But if we connect to a version 1 vdb, then deploy a version 2 vdb of same name, then once the version 2 vdb starts deploying we are not able to connect to version 1 vdb and a meaage comes VDB "Name" version "1" does not exist.
> Am I missing something?

--
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