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 Tue, 17 Jul 2012 15:44:33 GMT

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

Alexander Klimetschek commented on OAK-181:

{quote}If you want to copy the index data, then you do a full database backup.{quote}

Which will be simpler if there are no separate lucene index in the file system, but all inside
the repository (and hence in the repository persistence layer). That should be satisfied,
regardless whether those index nodes will be exposed via the JCR API or not.

But I still see the use case of copying via "packages" (built on top of the JCR API): if you
have one or more custom indexes for a large subtree, you can easily copy them over this way,
without having to run re-indexing on the target instance.
> 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