[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=13276402#comment-13276402 ] 

Steven Hawkins 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.

Because from a user perspective you have to update a property one time - not for each vdb/version, and yes hiding any other schema from odata as you say could be accomplished with a hidden schema. 

> Again the solution is more targeted for SF.

exclude-system-schema is not, but yes salesforce-safe-metadata is.  However it's unlikely that a user would want to omit/hide an entire schema because a single table/procedure contained an array type, so a targeted solution is probably what would needed outside of the system schema (which as we've already agreed can easily be omitted).

> SF might come along their support for Collections in next release, so, IMO we do not need to specifically target for that.

That is what I am saying - you would validate the sf integration before adding salesforce-safe-metadata to later branches.

What I'm advocating for is to just do exclude-system-schema for legacy branches.  If you feel like that seems incomplete, then I'm saying salesforce-safe-metadata is the next best solution.

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