[
https://jira.jboss.org/browse/TEIID-962?page=com.atlassian.jira.plugin.sy...
]
Steve Hawkins updated TEIID-962:
--------------------------------
Fix Version/s: 7.2
(was: 7.1)
Pushing to 7.2. The workaround starting in 7.0 is to use the File translator saveFile
procedure and SQLXML to produce an xml document form of the results. e.g.
<file model>.saveFile('newFile.xml', (select xmlelement("root",
xmlagg(xmlelement("row", xmlforest(c1, c2, c3 ...)))) from table ))
that would save the document:
<root>
<row><c1>val</c1><c2>val</c2>...</row>
...
</root>
Create new system function to dump temp table contents to file.
-----------------------------------------------------------------
Key: TEIID-962
URL:
https://jira.jboss.org/browse/TEIID-962
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 6.0.0
Environment: All
Reporter: Ken Johnson
Assignee: Steve Hawkins
Fix For: 7.2
A requirement to produce a CSV file reflecting the contents of a query result set so it
can be subsequently FTP'd or email'd. In Nov 07 implemented this feature using the
exec connector, a shell script and mods to JDBCISQL.
Suggested capability: function will take the following parameters:
- Temp table name as string
- Target file name (path qualified) as string
- Delimiter as string
When invoked, the specified temp table contents will be written out to the specified file
using the specified delimiter to separate the column values.
This generic capability will allow the CSV file thats needed and subsequently process it
with other UDF functionality as necessary.
Open questions:
1. How does file path behave in a clustered environment? Is it relative to the MM Server
install dir or fully qualified?
Suggest this feature remain undocumented for the short term.
--
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