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

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

The solution being provided is to exclude any schema from the $metadata document based on a configuration setting in the web.xml of teiid-odata.war file. The schema exclusion list can be made per VDB. To enable this, open the teiid-odata.war file using zip utility and un-comment following property

{code}
    <context-param>
        <param-name>exclude-schemas-from-metadata</param-name>
        <param-value>vdb.1.SYS,vdb.1.SYSADMIN</param-value>
    </context-param>
{code}

Add correct schema names (comma separated and fully qualified names vdbname.version.schemaname), update war file. The undeploy the old and redeploy the new teiid-odata.war file.

The commit to pull into the build can be found here     https://github.com/rareddy/teiid/commit/8e6d7d05a6136aaf6eed241ed2452798a39b1417

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