[
https://jira.jboss.org/browse/TEIIDDES-521?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIIDDES-521:
---------------------------------------
TEXTTABLE is added as a SQL Command, not a Function. Where as "getTextFiles" ,
"getFiles" are procedures that are available through File Translator. The reason
they are not system functions is their dependency on the Fie Translator + File Resource
Adapter to make them work. System functions are free standing evaluated on their own.
What SteveH, suggesting is have a static model with these procedures defined in a Designer
library some where. When user says to create a File based model, then copy the static
model into user defined name. That's it. The same is true for Web Service model.
The other way is to read the metadata form the Teiid API to create model. This has much
more broader uses, as it caters for any translator that is "metadata-aware".
Add "importer" or model template for file translator
----------------------------------------------------
Key: TEIIDDES-521
URL:
https://jira.jboss.org/browse/TEIIDDES-521
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 7.0
Reporter: Steve Hawkins
Most commonly to use the TEXTTABLE table function (the replacement for the text
connector) the user will need to use a File Translator/File Resource Adapter. Since the
file translator only exposes a known set of procedures, this could be as simple as a model
copy. The other approach would be to use the translator api to get the metadata from the
translator and then turn that into a model.
This is also needed for the WS Translator/WS resource adapter. See TEIIDDES-464
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira