[
https://issues.jboss.org/browse/TEIIDDES-1303?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-1303:
----------------------------------------
Will there be a corresponding translator in Teiid? also we have had discussions earlier to
develop a generic importer to import metadata from the translator metadata. This issue has
been pushed due to time constrains before. If you are targeting this to 8.0, I advocate we
invest time in developing generic importer then make use of it for data sources like
OData, so that we do not have to do the metadata import once for the Designer VDB and once
for Dynamic VDB.
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