[teiid-issues] [JBoss JIRA] (TEIID-2517) Incorrect handling of Complex Type in OData Metadata Procedures

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-2517.
---------------------------------

        Labels: CR2  (was: )
    Resolution: Done


There were few issues fixed along with this issue

1) Complex return type support has been added for the "function import" executions.
2) Byte handling was in correct, in retrieving the data from odata source
3) When multiple parameter exist in a function import, a mal formed URL was being constructed.
4) DateTime types were not correctly escaped for function imports
5) The column ordering did not preserved from the user query during the evaluation in odata translator, thus can lead to mismatched results or errors  

                
> Incorrect handling of Complex Type in OData Metadata Procedures
> ---------------------------------------------------------------
>
>                 Key: TEIID-2517
>                 URL: https://issues.jboss.org/browse/TEIID-2517
>             Project: Teiid
>          Issue Type: Bug
>          Components: Misc. Connectors
>    Affects Versions: 8.3
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>              Labels: CR2
>             Fix For: 8.4
>
>
> FunctionImports that return ComplexTypes are not being handled correctly. The metadata load fails during the VDB deploy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira