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 2017/08/03 10:16:00 UTC
[jira] [Assigned] (OAK-6516) Consider reordering the
index-update-hook to reside with other post-commit-hooks
[ https://issues.apache.org/jira/browse/OAK-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela reassigned OAK-6516:
---------------------------
Assignee: angela
> Consider reordering the index-update-hook to reside with other post-commit-hooks
> --------------------------------------------------------------------------------
>
> Key: OAK-6516
> URL: https://issues.apache.org/jira/browse/OAK-6516
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core, indexing
> Reporter: angela
> Assignee: angela
>
> Currently the index-update hook is located together with other commit validators and is followed by the security related validators that are plugged to the final commit hook upon each call to {{Root.commit}} to allow for proper pluggability of security modules.
> Consequently a given commit may fail with some security related validation only after the index updated has been proceeded already.
> I would like to discuss the possibility to treat the index-update like a post-commit-hook that is only executed after all validation has been performed. In the security area this is achieved by collecting the validator separately from the post-commit-hooks.
> [~stillalex], [~tmueller], I would appreciate if we could discuss this topic as well as possible implications/regressions that might be associated with it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)