[
https://issues.jboss.org/browse/TEIID-5405?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-5405:
----------------------------------
Fix Version/s: 11.1
This behavior was part of the original odata logic and was preserved with the changes to
suppor semantic versions. The rationale I believe is that the best practice for odata is
to require explicit versioning. Perhaps this could be driven by a vdb property.
Change default vdb version behavior for Odata/Odata4 to use
Connection type like JDBC Connections
-------------------------------------------------------------------------------------------------
Key: TEIID-5405
URL:
https://issues.jboss.org/browse/TEIID-5405
Project: Teiid
Issue Type: Feature Request
Components: OData
Affects Versions: 8.12.13.6_4
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Fix For: 11.1
With JDBC/ODBC Connections having the Connection type set to BY_VERSION for all versions
of a VDB and not specifying the version in the URL it connects to the earliest version (as
it should) and setting the Connection type to ANY for the latest version of the VDB it
connects to that version by default if none is specified in the URL (this is also the
correct behavior) but connecting via OData/OData4 it will always connect to version 1 if
the version is not specified in the URL even if the latest VDB version has Connection type
of ANY and all others are set to BY_VERSION. Can the OData connection behavior be the
same as JDBC/ODBC?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)