Hello All,
I am not able to open my content fragment model to edit. Getting below mentioned error. Any help in this case?
Solved! Go to Solution.
Views
Replies
Total Likes
Hello @Mahesh_Gunaje,
The error says that AEM could not find a suitable index for the content fragment model and so it fell back to traverse node-by-node. Traversing is the last step that AEM takes when it cannot find an index to use, and it is very costly performance wise.
The error also provides the next steps to create an index matching the query path:
consider creating an index or changing the query
It also mentions that it stopped processing to avoid harm or slowing down AEM:
The query read or traversed more than 500000 nodes.
To avoid affecting other tasks, processing was stopped.
select [jcr:path], [jcr:score],
* from [dam:Asset] as a where [jcr:content/contentFragment] = 'true' and [jcr:content/data/cq:model] =
'/conf/abc/settings/dam/cfm/models/my-model' and isdescendantnode(a, '/content/dam') option(index tag [fragments])
Please refer to this Adobe documentation section on index creation,
thanks,
Preetpal
Hello @Mahesh_Gunaje,
The error says that AEM could not find a suitable index for the content fragment model and so it fell back to traverse node-by-node. Traversing is the last step that AEM takes when it cannot find an index to use, and it is very costly performance wise.
The error also provides the next steps to create an index matching the query path:
consider creating an index or changing the query
It also mentions that it stopped processing to avoid harm or slowing down AEM:
The query read or traversed more than 500000 nodes.
To avoid affecting other tasks, processing was stopped.
select [jcr:path], [jcr:score],
* from [dam:Asset] as a where [jcr:content/contentFragment] = 'true' and [jcr:content/data/cq:model] =
'/conf/abc/settings/dam/cfm/models/my-model' and isdescendantnode(a, '/content/dam') option(index tag [fragments])
Please refer to this Adobe documentation section on index creation,
thanks,
Preetpal
There have been some issues with the content fragment index. You might want to check release notes.
Which Service pack are you using currently?
There was one suggestion in https://docs.mktossl.com/docs/experience-manager-65/release-notes/service-pack/6.5.11.html?lang=en
When trying to move/delete/publish either Content Fragments or Sites/Pages, there is an issue when Content Fragment references are fetched, as the background query will fail; that is, the functionality will not work.
To ensure correct operation you need to add the following properties to the index definition node /oak:index/damAssetLucene
(no re-indexing is required) :
"tags": [
"visualSimilaritySearch"
]
"refresh": true
I am using 6.5.13 version. Added these details in damAssetLucene
"tags": [ "visualSimilaritySearch" ] "refresh": true
. Still same issue.
Views
Replies
Total Likes