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

[Ramesh Reddy (JIRA)]

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

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

What I can't seem to understand advantages why you proposing new solution over what I provided, which is general purpose in nature and works in both situations. I am placing this as feature where user has a way to exclude a schema based on their choice, rather than specific Salesforce specific. I advantage I see is, you will not eliminate whole schema, but only ones with collections types. Again the solution is more targeted for SF. SF might come along their support for Collections in next release, so, IMO we do not need to specifically target for that.

One argument I can  agree is, with visibility of the models we can control the schema inclusion already, then why a generic solution over it? The reason I did this way is, so that I can give choice to the user per VDB whether one could choose to hide system metadata or not. If you think that distinction is not really necessary then I am OK with changing to "exclude-system-metadata" property.

As per V4, it is not given that SF do not support Collections, AFAIK they do not have V4 support or there is no such limitation, so IMO there is no action needed there yet. If it proven that we need it then we can further look into the issue.

> 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: Johnathon Lee
>             Fix For: 8.12.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)