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 "angela (JIRA)" <ji...@apache.org> on 2016/11/10 09:31:59 UTC

[jira] [Updated] (OAK-4898) Allow for external changes to have a CommitInfo attached

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

angela updated OAK-4898:
------------------------
    Fix Version/s:     (was: 1.6)
                   1.8

> Allow for external changes to have a CommitInfo attached
> --------------------------------------------------------
>
>                 Key: OAK-4898
>                 URL: https://issues.apache.org/jira/browse/OAK-4898
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.8
>
>
> Currently the observation logic relies on fact that CommitInfo being null means that changes are from other cluster node i.e. external changes. 
> We should change this semantic and provide a different way to indicate that changes are external. This would allow a NodeStore implementation to still pass in a CommitInfo which captures useful information about commit like brief summary on what got changed which can be used for pre filtering (OAK-4796)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)