[
https://issues.jboss.org/browse/TEIID-5221?page=com.atlassian.jira.plugin...
]
Jan Stastny commented on TEIID-5221:
------------------------------------
[~shawkins] well we should be able to consume, what we produce in Teiid. So either include
ReferentialConstraint to the odata4 response, or be more flexible when importing from
odata4.
No immediate need for that to accompany this fix, I'll use different odata source for
now.
OData4 Translator generates invalid metadata
---------------------------------------------
Key: TEIID-5221
URL:
https://issues.jboss.org/browse/TEIID-5221
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors, OData
Affects Versions: 8.12
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 10.1, 10.0.3, 9.3.7, 8.12.12.6_4
The OData V4 translator does not generate metadata correctly in situations
1) When multiple navigations are defined on the EnitityType.
2) The PSEDEO column usage is incorrect, as this should be only used with ComplexType
structures when the association to EntityType is made. But this is also used in cases
where incorrect referential constraints are used. This may lead to the additional columns
on Entities which are hard to resolve during the runtime.
3) Usage of MERGE property is also incorrect when multiple navigation properties are
defined as these may be overridden for (1)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)