VDB Versioning misunderstanding?

[lukyer]

Hi,
i'm trying to use simple VDB versioning. I'm using just simple XML VDB deploy (placing into deployments dir):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<vdb name="test" version="1">

     <connection-type>ANY</connection-type> <!-- probably not necessary? -->

     <model name="test" type="VIRTUAL">

         <metadata type="DDL"><![CDATA[

CREATE VIEW myview as SELECT 'test';

]]> </metadata>

    </model>

</vdb>

After deployment I can connect into VDB using JDBC connection string jdbc:teiid:test@mm://127.0.0.1:31000;version=1
However if raise version number to 2, deploy it again with the same name, i cannot connect to the previous VDB version with mentioned connection string. Response:

13:27:28,446 WARN  [org.teiid.SECURITY] (NIO0)  TEIID40011 Processing exception 'TEIID40046 VDB "test" version "1" does not exist.' for session null.  Exception type org.teiid.client.security.LogonException thrown from org.jboss.teiid//org.teiid.services.SessionServiceImpl.createSession(SessionServiceImpl.java:172).: org.teiid.client.security.LogonException: TEIID40046 VDB "test" version "1" does not exist.

I have to use new version jdbc:teiid:test@mm://127.0.0.1:31000;version=2

How can I get working multiple (even older) versions of the same VDB in parallel?

Thanks.

[shawkins]

> How can I get working multiple (even older) versions of the same VDB in parallel?

More than likely you are hitting an issue with the deployment names, such that the second deployment is overriding the first.  You need unique deployment names to have multiple versions of the same vdb on the server.  That is why we also support specifying the version by convention as part of the deployment name.

[rareddy]

Read on VDB versions at [1] and then you can set the connection type as VDB property as shown in [2]. If you want to be able to connect to both vdbs, then keep both vdbs deployed.

[1] VDB Versioning · Teiid Documentation

[2] Using XML & DDL · Teiid Documentation

[lukyer]

Thanks Steven,
I was deploying all VDBs with the same names, different versions but, as you said, same deployment name (my-vdb.xml). To get versioning working you have to use unique deployment name, vdb name can remain the same.

I think it is an important fact you should include in docs. Please add it for better versioning understanding.

[rareddy]

Can you log a JIRA to keep track of this? Thanks.

[shawkins]

Resolved under [TEIID-5381] Add a doc note about deployment names - JBoss Issue Tracker