I made our own index as shown in the screenshot. A lucene-type index with many other indexing keys also. The issue is that when using cq:tags, oak-1.0.22 always picks up the OOTB one. I tried to make an alternative by getting rid of the OOTB one, which is always a bad idea, it turned out that there ...
That's correct, but it will consume a lot of cpu power if the site gets hit at a certain level. Plus, when it drops the query at the limit, say, 100k nodes, the result set is not always accurate because the more precise records may be left behind.
Hi @aanchal-sikka,
It looks like oak doesn't know how to limit the query size for some reason. My understanding is that if a query limits to a certain path, say, /jcr:root/a/b/c, the space complexity shouldn't be more than the total nodes under that path. I issue a query to a certain path with onl...
Hi Kiran,
No the path is very specific. I actually did a very simple query as:
/jcr:root/content/site/departments/film-tvs/courses/2022-fall//element(*, cq:PageContent)
It traverses 80000 nodes even if there are less than 100 pages under that directory. The similar issue you are referring is a h...
Hi all,
We have an issue for the AEM6.0/oak-1.0.22 indexing issue. There a lot of warning messages like:
org.apache.jackrabbit.oak.plugins.index.property.strategy.ContentMirrorStoreStrategy Traversed 80000 nodes (280221 index entries) using index cq:tags with filter Filter(query=select [jcr:path],...
Hi All, We started seeing a weird issue about query optimization a few months ago. When we issue a query as:/jcr:root/content/site//element(*,cq:PageContent)[@sling:resourceType='site/components/page/news-detail' and (@cq:tags = 'department:drama')] order by @date descendingWe will see a warning mes...
Hi @Himanshu_Singhal , Thanks for your reply.I don't see the "consider creating an index or changing the query" in the error log, and it is not supposed to be there because I created all the necessary customized indexes under oak:index, plus the specific targeted content directory "/content/a/b" has...
Hi All, We found the oak running into a problem consuming a lot of resources so we are trying to improve the XPath queries. Our AEM is 6.0 on OAK 1.0.22. According to https://jackrabbit.apache.org/oak/docs/query/query-troubleshooting.html, queries should not traverse more than 1000 nodes. We start o...