[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated OAK-5788: -- Attachment: OAK-5788.patch > 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 >Assignee: Marcel Reutegger > Labels: performance > Fix For: 1.8 > > Attachments: OAK-5788.patch > > > 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.4.14#64029)
[jira] [Updated] (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:all-tabpanel ] Chetan Mehrotra updated OAK-5788: - Labels: performance (was: ) > 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 > Labels: performance > 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)
