[teiid-issues] [JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

Ramesh Reddy (JIRA) issues at jboss.org
Wed Aug 3 11:56:00 EDT 2016


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

Ramesh Reddy commented on TEIID-4271:
-------------------------------------

[~shawkins] I believe in OData v2, there is limited support for collection types, OData V3 added some of it. OData V4 lots of stuff uses collection types, so an implementation not supporting collections is just not usable IMO. 

So, considering this applies to only OData V2, we can target this to JDV 6.3 scoped build. May be we should just reject here and work with BZ.

> Consume Teiid OData from Salesforce
> -----------------------------------
>
>                 Key: TEIID-4271
>                 URL: https://issues.jboss.org/browse/TEIID-4271
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: OData
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>             Fix For: 9.x
>
>
> At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String).  Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume.  If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume.
> Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this.  And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the teiid-issues mailing list