[
https://issues.jboss.org/browse/TEIID-5182?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5182.
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
Resolution: Done
Marking as resolved on the upstream side. Will this go into 6.4 proactively or wait for a
fix pack?
OData4 Imported MXD properties have a space
-------------------------------------------
Key: TEIID-5182
URL:
https://issues.jboss.org/browse/TEIID-5182
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Critical
Fix For: 10.1
The Metadata Extension Properties that are imported from server for OData4 translator
have leading space in the definition, thus it creates a wrong VDB which fails to run
during the runtime
{code}
<p:property advanced="false" index="true"
masked="false" name="Type" required="true"
type="string">
<p:allowedValue>COMPLEX</p:allowedValue>
<p:allowedValue> NAVIGATION</p:allowedValue>
<p:allowedValue> COMPLEX_COLLECTION</p:allowedValue>
<p:allowedValue> ENTITY_COLLECTION</p:allowedValue>
<p:allowedValue> NAVIGATION_COLLECTION</p:allowedValue>
<p:allowedValue> ENTITY</p:allowedValue>
<p:allowedValue> FUNCTION</p:allowedValue>
<p:allowedValue> ACTION</p:allowedValue>
</p:property>
{code}
see allowed Values with leading white space. I am not sure this is how the server is
providing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)