You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Christoph Deppisch (Jira)" <ji...@apache.org> on 2020/08/19 07:35:00 UTC

[jira] [Work started] (CAMEL-15407) Merge operation in camel-olingo2 sets all entity properties to null

     [ https://issues.apache.org/jira/browse/CAMEL-15407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-15407 started by Christoph Deppisch.
--------------------------------------------------
> Merge operation in camel-olingo2 sets all entity properties to null
> -------------------------------------------------------------------
>
>                 Key: CAMEL-15407
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15407
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-olingo2
>    Affects Versions: 3.x
>            Reporter: Christoph Deppisch
>            Assignee: Christoph Deppisch
>            Priority: Major
>             Fix For: 3.5.0
>
>
> The merge operation in OData V2 can be used to update individual fields on an entity. The operation should perform an incremental update without replacing all the contents of an entry. In particular the request updates only the properties indicated in the request body, and leaves untouched any other property not mentioned in its current state.
> When the camel-olingo2 component performs the merge operation all fields are updated - also the not mentioned properties. Those fields not mentioned in the request body are set to null by default.
> This behavior is controlled by the EntityProvider write property called "isDataBasedPropertySerialization". By default this setting is set to false resulting in non present fields to be set to null by default. For merge operations this setting should be enabled by default in order to just update the mentioned fields in the request body.



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