[teiid-issues] [JBoss JIRA] (TEIID-2666) Extend OData output formats, currently JSON and XML supported

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968213#comment-12968213 ] 

Steven Hawkins edited comment on TEIID-2666 at 5/15/14 2:22 PM:
----------------------------------------------------------------

> It's really computationally intensive and expensive to have to reformat the JSON responses coming out of Teiid.

Sorry the formatting above was initially throwing me.  So effectively you want to omit the metadata and change the result collection name.  From what I can see there is odata 3 functionality somewhat similar to this with the odata metadata options (no metadata, minimal metadada, or full metadata).  However none of those options seem to use the entity name for the collection name.

As we will likely be moving away from OData4j and toward olingo for odata 3 support, I don't think we should do more patching of odata4j than necessary.


was (Author: shawkins):
> It's really computationally intensive and expensive to have to reformat the JSON responses coming out of Teiid.

It's not clear to me from the above what exactly you are looking for.  Can you provide more context as to what the result represents and how/why you get the alternate form?  Generally this breaks down along the lines of:

1. Is there an OData4j formatting bug?
2. Are you suggesting that is a compatible with the spec?
3. Is this something that is simply custom?


> 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)