[ https://issues.jboss.org/browse/TEIID-3543?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3543: ------------------------------------- Yes, previously we would have been showing the entity type with complex type folded in, this will change that. The whole issue arises from using the same EDM parsing module for translator and on out OData service. Translator EDM parser should be exactly same as what source represents. The outbound one is our interpretation of Teiid schema to OData schema. This was bad choice on my part, which I did not foresee before. This also raises the question of whether we need to move some of the extension metadata from translator specific to engine level to give freedom to the user how they define OData metadata. For now we need to test complex property navigation is still works with V2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)