You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/02/23 14:00:48 UTC
[jira] [Commented] (OAK-5788) Perform update of single node in one
remote call if possible
[ https://issues.apache.org/jira/browse/OAK-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880455#comment-15880455 ]
Chetan Mehrotra commented on OAK-5788:
--------------------------------------
Added testcase in 1784132. It sets a property /a/b@foo=bar resulting in following calls
{noformat}
createOrUpdate key: 2:/a/b update {_commitRoot.r15a6b406e14-0-1=SET_MAP_ENTRY 2, foo.r15a6b406e14-0-1=SET_MAP_ENTRY "bar", _modified=MAX 1487858065}
findAndUpdate key: 2:/a/b update {_commitRoot.r15a6b406e14-0-1=REMOVE_MAP_ENTRY null, foo.r15a6b406e14-0-1=SET_MAP_ENTRY "bar", _modified=MAX 1487858065, _revisions.r15a6b406e14-0-1=SET_MAP_ENTRY c} conditions {_collisions.r15a6b406e14-0-1=EXISTS false}
{noformat}
> Perform update of single node in one remote call if possible
> ------------------------------------------------------------
>
> Key: OAK-5788
> URL: https://issues.apache.org/jira/browse/OAK-5788
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Chetan Mehrotra
> Fix For: 1.8
>
>
> If a single node is modified in a commit then currently it performs 2 remote calls
> # The actual update
> # Update of commit root
> as for single node update commitRoot == node being updated we can optimize this case to see if both operations can be done in same call
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)