Chetan Mehrotra commented on OAK-4907:

bq. In theory it should also be OK for the ChangeCollector to add a new 
CommitContext (which it indeed doesn't do now) when it's not there - and in 
this case the check for EMPTY would avoid that.

Yes that would have been ideal. See OAK-4640 for background on why this route 
was not taken

> Collect changes (paths, nts, props..) of a commit in a validator
> ----------------------------------------------------------------
>                 Key: OAK-4907
>                 URL: https://issues.apache.org/jira/browse/OAK-4907
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: core
>    Affects Versions: 1.5.11
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.6
>         Attachments: OAK-4907.patch, OAK-4907.v2.patch
> It would be useful to collect a set of changes of a commit (eg in a 
> validator) that could later be used in an Observer for eg prefiltering.
> Such a change collector should collect paths, nodetypes, properties, 
> node-names (and perhaps more at a later stage) of all changes and store the 
> result in the CommitInfo's CommitContext.
> Note that this is a result of 
> [discussions|https://issues.apache.org/jira/browse/OAK-4796?focusedCommentId=15550962&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15550962]
>  around design in OAK-4796

This message was sent by Atlassian JIRA

Reply via email to