[
https://issues.apache.org/jira/browse/OAK-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681150#comment-13681150
]
Jukka Zitting commented on OAK-763:
-----------------------------------
I prefer to keep the checkpoint mechanism a bit separated from the branch
concept, as their semantics are different. A checkpoint is a longer-term
read-only concept that's visible to all clients (that have the correct string
reference), whereas a branches is a (typically) short-lived read-write concept
that's visible to just one client.
The rationale for the {{branch(String checkpoint)}} (instead of the
{{retrieve(String checkpoint)}} I proposed earlier on oak-dev@) is the way our
commit hooks use the {{after}} state as the base for any content modifications.
Thus it is more convenient if the {{after}} state comes from a branch. A
potentially better alternative might be to replace the commit hook in
{{AsyncIndexUpdate}} with direct use of the {{IndexUpdate}} class.
> Asynchronous indexing
> ---------------------
>
> Key: OAK-763
> URL: https://issues.apache.org/jira/browse/OAK-763
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Attachments: OAK-763-mv-scheduler.patch, OAK-763.patch,
> OAK-763-v2.patch, OAK-763-v4.patch
>
>
> It would be good to have the possibility to update indexes asynchronously,
> outside the current commit hook (or editor).
> This would be used for the index impls which can be a bit behind, like the
> ones that do text extraction from binaries.
--
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
