[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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=63364#comment-63364 ] Michael Pizzo commented on ODATA-818: ------------------------------------- Added new preference with all semantics except: 4) If the client doesn't specify an OData-MaxVersion header the service is free to omit nulls. ==>in this case, would the service still be allowed to return an OData-Version header? Would it need to specify the preference, even though it wasn't requested? > 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 [Proposed] > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]