[
https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4271:
---------------------------------------
Turning off for all VDBs seemed too intrusive to me.
It's unlikely that system model metadata access is needed over odata in any case as
the full metadata is published. Also for each vdb/version the servlet parameters would
need to be updated.
To address for salesforce in general, we could have another property that excludes any
table/procedure that has an array type. However just based upon the case only the
exclusion of the system metadata is needed for now.
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)