[
https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2666:
---------------------------------------
As Ramesh say this would require odata4j to support extensible formats since they are
unlikely to add direct support for csv - which from the odata mailing lists there is
resistance toward considering in general given the lack of metadata and lack of a standard
way to represent hierarchical data.
Assuming xml/atom and applying xslt on top while conceptually simple would still require
an odata4j extension - and would require even more changes on their side as the format
strings would not be fixed.
So for us to pursue this it would have to be pretty high value as we'd likely end up
with temporary (or permanent) patches against odata4j.
Extend OData output formats, currently JSON and XML supported
-------------------------------------------------------------
Key: TEIID-2666
URL:
https://issues.jboss.org/browse/TEIID-2666
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.4
Environment: N/A
Reporter: Cojan van Ballegooijen
Assignee: Steven Hawkins
Priority: Trivial
We would like to see the available output formats of the OData services be extended with
CSV (Command Seperated Values) upon customer request.
It would be great if we could extend it ourselves using for example XSLT or other
transformation mechanism.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira