[teiid-issues] [JBoss JIRA] (TEIID-5182) OData4 Imported MXD properties have a space

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511296#comment-13511296 ] 

Ramesh Reddy commented on TEIID-5182:
-------------------------------------

This needs to go into 6.4, maybe [~vhalbert2] can create a BZ and track it. Since this only affects odata4 based source imports it can wait till the first patch, if not if there is build we can pull in to the current 6.4 branch.

> 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)