[
https://issues.jboss.org/browse/TEIID-3548?page=com.atlassian.jira.plugin...
]
Ramesh Reddy reassigned TEIID-3548:
-----------------------------------
Assignee: Steven Hawkins (was: Ramesh Reddy)
In light of your comments should we keep as is? Not sure how much benefit this gives other
than it mimics the imported $metadata if model imported from OData service.
In much larger picture, we have different properties in JPA and MongoDB in similar
places.
Another idea is defining the tables without PK or Unique keys as complex types, so that we
do not omit them as we do currently.
Creation of embedded complex not supported by odata production
--------------------------------------------------------------
Key: TEIID-3548
URL:
https://issues.jboss.org/browse/TEIID-3548
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
Prior to 8.11 we would always produce the flattened version with or without the complex
type extension metadata. With TEIID-3543 the extension metadata will cause production to
throw an exception. The workaround until this is fixed is to not use the complex type
extension metadata.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)