Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-818) Omit properties whose value is null or the $metadata-defined default value

From
OASIS Issues Tracker <>
Date
2016-04-29T18:26:57+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-818) Omit properties whose value is null or the $metadata-defined default value
[ https://issues.oasis-open.org/browse/ODATA-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62337#comment-62337 ] 

Michael Pizzo commented on ODATA-818:
-------------------------------------

Also need to think about delta responses, since we allow properties to be omitted that have not changed. In this case, I would assume that a property whose value was changed to null would have to be represented in the payload?

> Omit properties whose value is null or the $metadata-defined default value
> --------------------------------------------------------------------------
>
>                 Key: ODATA-818
>                 URL: https://issues.oasis-open.org/browse/ODATA-818
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: Simplified Payload
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Performance
>             Fix For: V4.01_WD01
>
>
> Entities with many properties that are sparsely filled would benefit from optimizing the payload and omitting properties whose value is null.
> With odata.metadata=minimal the client can deduce from the context URL whether a property is missing due to not being part of the projection or due to being null.
> Maybe switch this on/off via a new preference in the Prefer header.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →