You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@olingo.apache.org by Ronny Bremer <rb...@almanid.com> on 2015/08/04 00:48:28 UTC

OData V2 and $select

When I use a $select=Col1,Col2 parameter in my ODataV2 server servlet implementation, it looks like the library is going to ignore that completely.

I can successfully retrieve the SelectItemList from the uriInfo parameter in both readEntity() and readEntitySet() and made sure, that my responseData parameter passed into EntityWriter.write does only contain the requested properties.
However, the JSON on the wire will still contain the entire schema with all unrequested properties set to null.

This does not seem to be the intended behaviour, at least in my eyes.

Is there anything I am missing? Shouldn’t the library be aware of the $select parameter use and not populate the entire schema during the response?

Thank you for your time,

Ronny

Re: OData V2 and $select

Posted by Ronny Bremer <rb...@almanid.com>.
Done. Thank you for the suggestion!

Yours,

Ronny

> On 04 Aug 2015, at 06:36, mibo <mi...@apache.org> wrote:
> 
> Hello Ronny,
> 
> Thanks for reporting that issue.
> It would be very helpful when you could create an according issue at: https://issues.apache.org/jira/browse/OLINGO
> This helps us to track and fix the probable issue.
> 
> Best Regards,
> Michael
> 
>> Am 04.08.2015 um 00:48 schrieb Ronny Bremer <rb...@almanid.com>:
>> 
>> When I use a $select=Col1,Col2 parameter in my ODataV2 server servlet implementation, it looks like the library is going to ignore that completely.
>> 
>> I can successfully retrieve the SelectItemList from the uriInfo parameter in both readEntity() and readEntitySet() and made sure, that my responseData parameter passed into EntityWriter.write does only contain the requested properties.
>> However, the JSON on the wire will still contain the entire schema with all unrequested properties set to null.
>> 
>> This does not seem to be the intended behaviour, at least in my eyes.
>> 
>> Is there anything I am missing? Shouldn’t the library be aware of the $select parameter use and not populate the entire schema during the response?
>> 
>> Thank you for your time,
>> 
>> Ronny
>

Re: OData V2 and $select

Posted by mibo <mi...@apache.org>.
Hello Ronny,

Thanks for reporting that issue.
It would be very helpful when you could create an according issue at: https://issues.apache.org/jira/browse/OLINGO
This helps us to track and fix the probable issue.

Best Regards,
Michael

> Am 04.08.2015 um 00:48 schrieb Ronny Bremer <rb...@almanid.com>:
> 
> When I use a $select=Col1,Col2 parameter in my ODataV2 server servlet implementation, it looks like the library is going to ignore that completely.
> 
> I can successfully retrieve the SelectItemList from the uriInfo parameter in both readEntity() and readEntitySet() and made sure, that my responseData parameter passed into EntityWriter.write does only contain the requested properties.
> However, the JSON on the wire will still contain the entire schema with all unrequested properties set to null.
> 
> This does not seem to be the intended behaviour, at least in my eyes.
> 
> Is there anything I am missing? Shouldn’t the library be aware of the $select parameter use and not populate the entire schema during the response?
> 
> Thank you for your time,
> 
> Ronny