[
https://issues.jboss.org/browse/TEIIDDES-1303?page=com.atlassian.jira.plu...
]
Ted Jones commented on TEIIDDES-1303:
-------------------------------------
This is being pushed because we can/will handle OData with our XML importer in 7.7.1.
There are a few Jira's that will be worked for 7.7.1 to better support OData, but we
can claim support starting with that release. The importer that this Jira refers to will
interrogate the metadata served up by an OData service and will be custom tailored to any
generic OData server including SAP Gateway. There will likely be a new translator as well,
but that is yet to be determined.
Create OData Importer
---------------------
Key: TEIIDDES-1303
URL:
https://issues.jboss.org/browse/TEIIDDES-1303
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 7.7
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 8.0
To provide support for more complicated OData use cases, we should extend the XML
Importer to create an OData importer. This importer will read the metadata of the service
in the selected CP and determine what columns are allowable for input. We would then need
to create an access pattern on the generated base table for these fields. These fields
would be added to the URL of the service.. so the above Bank service URL would become:
http://gw.esworkplace.sap.com/sap/opu/sdata/sap/DEMO_BANK/z_demo_bankColl...
and the generated transformation should take the column values from the access pattern
and build the URL accordingly in the invokeHttp() call.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira