


More specifically, when attempting to edit a content fragment model the process fails:
The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.
After some investigation is looks like this query may be the culprit:
select [jcr:path], [jcr:score], * from [dam:Asset] as a where [jcr:content/contentFragment] = 'true' and
[jcr:content/data/cq:model] = '/conf/we-retail/settings/dam/cfm/models/test' and
isdescendantnode(a, '/content/dam') option(index tag [fragments])
/* xpath: /jcr:root/content/dam//element(*, dam:Asset)[(jcr:content/@contentFragment = 'true' and
jcr:content/data/@cq:model = '/conf/we-retail/settings/dam/cfm/models/test')] option (index tag fragments) */
On my server /content/dam is quite large. Assuming this reference is indeed the problem, is it possible to change it?
Solved! Go to Solution.
Views
Replies
Sign in to like this content
Total Likes
Hi @BobNoelle ,
Are you facing this issue with AEM6.5 or AEM Cloud? Also, mention the service pack installed.
This looks like a known issue and the fix was provided with SP12, check here:-
Try to install the package related to the index as mentioned in the section
Hope that helps!
Regards,
Nitesh
Hi @BobNoelle ,
Are you facing this issue with AEM6.5 or AEM Cloud? Also, mention the service pack installed.
This looks like a known issue and the fix was provided with SP12, check here:-
Try to install the package related to the index as mentioned in the section
Hope that helps!
Regards,
Nitesh
I'm currently at aem-service-pkg-6.5.12.0.zip and I'm working on AEM6.5. I apologize for being scant on the details of my environment, but you guessed correctly. I tried installing service pack 6.14 but the issue was still present, however installing cfm-graphql-index-def-1.0.3.zip resolved the problem. Many thanks.
When will the issue fixed? The latest Servicepack is 16 and it seems the issue does still exists.