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.

Complex type values not resolved in translator execution -------------------------------------------------------- Key: TEIID-3543 URL: https://issues.jboss.org/browse/TEIID-3543 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 Embedded complex types do not have metadata associated and will fail to resolve resulting in an exception: {code} java.lang.RuntimeException: unknown property type: RMTSAMPLEFLIGHT.FlightDetails at org.odata4j.format.xml.AtomFeedFormatParser.parseProperties(AtomFeedFormatParser.java:210) ~[odata4j-core-0.8.0-SNAPSHOT-redhat.jar:na] {code}