[
https://issues.apache.org/jira/browse/OAK-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639081#comment-13639081
]
Alex Parvulescu commented on OAK-673:
-------------------------------------
hmm, it is indeed related to the order of editors, but I don't think it's the
same issue.
So assuming we've merged all editors in, what happens is that the VersionEditor
creates a version node (with a uuid property) that is missed by the indexer
because there's no #proeprtyChanged even fired, so the property index is not
updated.
Next when the test tried to load the node by id, it fails because the index
does not contain that entry.
Separating the version from the index in 2 different commit hooks works because
the indexer will pickup the changes that the version editor did.
> Unified hook processing
> -----------------------
>
> Key: OAK-673
> URL: https://issues.apache.org/jira/browse/OAK-673
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Attachments: OAK-673-VersionHook.patch
>
>
> As [discussed|http://markmail.org/message/xqw3yg3z5rnsiwz3] on oak-dev@, it
> would be good reduce the number of separate content diffs that various hooks
> do during each commit. To do this without having to merge unrelated
> functionality into one big hook class we should come up with a new hook
> generalization, like the one I
> [proposed|http://markmail.org/message/bydje7rf3si67fc3], that allows multiple
> independent components to process the results of a single content diff.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
