[
https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin...
]
John Muller commented on TEIID-2666:
------------------------------------
Thanks Steven, I wasn't aware of the move to Apache Olingo, but we'd really look
forward to OData V4 aggregate support down the road. You have our use case exact: mobile
apps consuming OData endpoints want a "clean" JSON object (single row) or array
(multiple rows) with the entity name set to be the collection name and no metadata aside
from the "nextLink"
Is there a JIRA feature request out for Olingo, or is that driven internally?
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
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 was sent by Atlassian JIRA
(v6.2.3#6260)