jackrabbit-oak-dev mailing list archives

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

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

Thomas Mueller commented on OAK-181:
------------------------------------

To allow managing indexes using the JCR API, the nodes that _define_ the indexes can and probably
should be regular nodes (including validation, access right, observation). The index content
itself (if stored in the repository) however should be invisible (no read access, no observation
and so on).
                
> 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

        

Mime
View raw message