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

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-4271:
---------------------------------------

In a forward looking sense this needs to be looked at for OData 4 as the OData 2 service has been removed.  Also this was written from the perspective of older releases - the SYS/SYSADMIN schemas now also have array types.

A vdb could use a property to exclude system metadata from odata metadata, but that would only be needed for legacy branches. 

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