You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by Apache Wiki <wi...@apache.org> on 2012/02/03 11:41:01 UTC

[Jackrabbit Wiki] Update of "IndexingConfiguration" by alexparvulescu

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "IndexingConfiguration" page has been changed by alexparvulescu:
http://wiki.apache.org/jackrabbit/IndexingConfiguration?action=diff&rev1=12&rev2=13

Comment:
recursive aggregates update

    </aggregate>
  </configuration>
  }}}
+ 
+ 
+ As of Jackrabbit 2.3.2, [[https://issues.apache.org/jira/browse/JCR-2989|JCR-2989]] allows for recursive aggregates. This allows for a pretty powerful definition of hierarchy of aggregates, but it also can very easily get out of hand [0].
+ 
+ This feature can be enabled by setting the '''recursive''' flag to ''true''.
+ 
+ {{{
+ <aggregate primaryType="nt:folder" recursive="true" recursiveLimit="10">
+ }}}
+ 
+ The '''recursiveLimit''' setting controls the number of levels up the indexing should include for same node types. The default value is ''100'', and setting it to ''0'' will give you support for full inclusion without any upper bound.
+ 
+ {{{[0] see }}} [[https://issues.apache.org/jira/browse/JCR-2989?focusedCommentId=13051101&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13051101|this comment]] {{{for an example of a scenario where indexing aggregates can hurt performance}}}
  
  
  === Index Analyzers ===