[ 
https://issues.apache.org/jira/browse/OLINGO-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246992#comment-17246992
 ] 

Kasun Eranga Kumarasinghe commented on OLINGO-1479:
---------------------------------------------------

With what release can we expect this?

> Allow system query option select and expand for PUT/PATCH requests
> ------------------------------------------------------------------
>
>                 Key: OLINGO-1479
>                 URL: https://issues.apache.org/jira/browse/OLINGO-1479
>             Project: Olingo
>          Issue Type: Bug
>            Reporter: Ramya Vasanth
>            Priority: Major
>
> Olingo V4 throws an exception when $select or $expand are used on a PUT or 
> PATCH request. However the specification states that this can be used to 
> control the returned data from the PUT or PATCH request:
> [https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_UpdateanEntity]
>  * Upon successful completion the service responds with either [200 
> OK|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_ResponseCode200OK]
>  and a representation of the updated entity, or [204 No 
> Content|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_ResponseCode204NoContent].
>  The client may request that the response SHOULD include a body by specifying 
> a [Prefer 
> header|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Preferencereturnrepresentationandret]
>  with a value of 
> [return=representation|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Preferencereturnrepresentationandret],
>  or by specifying the system query options 
> [$select|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_SystemQueryOptionselect]
>  or 
> [$expand|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_SystemQueryOptionexpand].
>  If the service uses ETags for optimistic concurrency control, the entities 
> in the response MUST include ETags.
> Hence we can remove this validation in Olingo
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to