[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3462:
-------------------------------------
So you will expand the "vdb-name" to allow (include) the semantic version, but
at deployment time parse the vdb-name with defined rules of the semantic versioning and
qualifiers. Then you will extend the current "connect by" to semantic version. I
am kind of still confused how you going to deal with the semantic version in system
metadata, sysadmin, Admin API, any external api methods etc., they all seem large changes
to me. Luckily I see that SYS only uses vdb-name and only uses "version" in
VirtualDatabases table.
Add support for semantic versioning of VDBs
-------------------------------------------
Key: TEIID-3462
URL:
https://issues.jboss.org/browse/TEIID-3462
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.7
Reporter: Marc Shirley
Assignee: Steven Hawkins
Fix For: 9.0
Semantic versioning [1] should be supported in the VDB versioning in order to be able to
easier determine whether there are breaking changes from the client perspective and to
more easily establish a link between client software versions and the VDBs they rely
upon.
[1]
http://semver.org/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)