[ https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379198#comment-14379198 ]
Alexander Klimetschek commented on SLING-4512: ---------------------------------------------- Ok, I attached a patch over in SLING-4543 that is not based on this one and keeps the query. Since I simplified the general logic of that complex {{loadFully}}, I suggest the fix here should be added on top of that patch. I can do so tomorrow. > Traversal Warnings in OAK while creating i18n JcrResourceBundle > --------------------------------------------------------------- > > Key: SLING-4512 > URL: https://issues.apache.org/jira/browse/SLING-4512 > Project: Sling > Issue Type: Improvement > Components: Extensions > Reporter: Srijan Bhatnagar > Assignee: Amit Gupta > Attachments: SLING-4512.diff > > > org.apache.sling.i18n.impl.JcrResourceBundle#loadFully uses an XPath query to > load [sling:Message] nodes under given paths. If the subtree under the path > is too big (>1000), we receive traversal warnings in Oak. The following > warning is generated if the path is /libs/wcm/core/i18n/de : > {code} > GET /content/geometrixx/de.html HTTP/1.1] > org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 1000 > nodes with filter Filter(query=select [jcr:path], [jcr:score], * from > [sling:Message] as a where isdescendantnode(a, '/libs/wcm/core/i18n/de') /* > xpath: /jcr:root/libs/wcm/core/i18n/de//element(*,sling:Message) */, > path=/libs/wcm/core/i18n/de//*); consider creating an index or changing the > query > {code} > A suggestion would be to use > [TreeTraverser|http://jackrabbit.apache.org/api/2.4/org/apache/jackrabbit/commons/flat/TreeTraverser.html] > instead of XPath query since the subtree is mostly a flat list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)