We have an images folder for our project in ASSETS section, which has more than 1000 images in it. Whenever the authors access that images folder through Assets section (http://localhost:4502/assets.html/content/dam/abc/content-images), the following warning is printed in the logs, which warns about the missing index for the query that is fired when that images folder is accessed.
*WARN* GET /assets.html/content/dam/abc/content-images HTTP/1.1] org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor Traversed 1000 nodes with filter Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where ischildnode(a, '/content/dam/abc/content-images') and [hidden] = 'false' union select [jcr:path], [jcr:score], * from [nt:base] as a where ischildnode(a, '/content/dam/abc/content-images') and [hidden] is null order by [jcr:created] desc /* xpath: /jcr:root/content/dam/abc/content-images/*[((@hidden = 'false' or not(@hidden)))] order by @jcr:created descending */, path=/content/dam/abc/content-images/*, property=[hidden=[false]]); consider creating an index or changing the query
We have not yet created any custom index for damAssets, as the above query is automatically fired by AEM when navigating through the Assets section and as there is no custom implementation done by us, we didn't create any index.
For analysis, I tried to run the above query and a simplified version of the above query - select [jcr:path], [jcr:score] from [nt:base] as a where ischildnode(a, '/content/dam/abc/content-images') through Explain Query tool and it mentions that no indexes were used in the query and it is a traversal query. The results are still returned with this query as well and it prints the same warning.
Has anyone else has found such warnings when navigating through assets? Looking for some help from the community here.
Checking this with the team!!
It certainly appears that the warning is because there is no Index here.
smacdonald2008 Yes, the warning clearly says consider creating an index. But this warning is appearing only in Author instance when accessing a particular folder in Assets and the query being printed in the warning seems to be internally fired by AEM. Ideally damAssetLucene index should take of all these index requirements where no custom development/customization has been done. What do you think?