You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/04/14 15:14:06 UTC

[jira] [Created] (JCR-2947) Index aggregate rule improvements

Index aggregate rule improvements
---------------------------------

                 Key: JCR-2947
                 URL: https://issues.apache.org/jira/browse/JCR-2947
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
          Components: indexing, jackrabbit-core
            Reporter: Jukka Zitting
            Priority: Minor


The current aggregate rules in indexing configuration are not very flexible. It would be great if aggregates could be triggered also by mixin types or more generic path and/or property constraints as done with other indexing rules. The include settings could also be more flexible, and there are cases where excludes would also be useful.

For example one use case we have is being able to define an aggregate for a my:document type that may have other my:document nodes within the subtree. The aggregate should contain the entire my:document subtree, *except* for any sub-my:documents. Also, the sub-my:document nodes would not need to be indexed as aggregates.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira