jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-181) Observation / indexing: don't create events for index updates
Date Fri, 13 Jul 2012 15:19:34 GMT

    [ https://issues.apache.org/jira/browse/OAK-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413811#comment-13413811

Alexander Klimetschek commented on OAK-181:

But the index should be part of the repository (e.g. as binary nt:files), so you can easily
back them up and copy over using the JCR API (and package systems on top of it). IIUC, that
is one of the major reasons to put indexes into the repository.

When copying such an index into another repository (i.e. writing the index file), the user/application
should have control over whether the index will be updated based on the repository's maybe
different contents or whether the index should simply be used as is. If the user knows the
content is the same, the index doesn't have to be updated and this can save re-indexing time.
Especially for large repositories this can come in very handy.
> Observation / indexing: don't create events for index updates
> -------------------------------------------------------------
>                 Key: OAK-181
>                 URL: https://issues.apache.org/jira/browse/OAK-181
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>            Reporter: Thomas Mueller
> If index data is stored in the repository (for example under jcr:system/oak:indexes),
then each change in the content might result in one or multiple changed in the affected indexes.
> Observation events should only be created for content changes, not for index changes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message