[
https://issues.jboss.org/browse/TEIIDDES-3151?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-3151:
----------------------------------------
[~blafond] The DDL is the one that defines all metadata *always*. If there are any archive
specific properties like security, rest war generation those properties can be in the VDB
level properties.
The odata4.mxd is the custom mxd I tried to use in my workspace where I changed the
namespace of the odata schema coming in from server (I simply used DDL based import, where
I edited the namespace in the file) because I could not edit/modify the built-in
odata.mxd.
But as I noted in the previous comment, the odata v2 and odata v4 metadata from the server
use exactly *SAME* namespace, that means the properties in odata.mxd need to be updated
as opposed to creating a new namespace for odata v4. If you want you can add some comments
in the description as to which property belongs to which version. Alternatively Teiid can
create a new namespace for the odata v4, but that will be a break in compatibility, and
previously created VDBs will no longer work.
OData4 specific MXD is not found
---------------------------------
Key: TEIIDDES-3151
URL:
https://issues.jboss.org/browse/TEIIDDES-3151
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 11.1
Reporter: Ramesh Reddy
Assignee: Barry LaFond
Priority: Blocker
Fix For: 11.1.1
Attachments: odata4.mxd
While working on the case I found that there is no "odata4" specific MXD nor
the current odata MXD is updated with newer properties for the V4. Since server uses the
same namespace the current one needs to be updated.
A sample MXD (minus the namespace) is attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)