I think locally using CRX/DE you can manually add cfGlobalVersion=1 to /content/dam JCR node and it will do the job, you can find more info about the cloud procedure here https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/graphql-api/graphql-optimized-filter...

Hi @Preston The way AEM decides which index to use is based on the cfGlobalVersion property of /content/dam node.If the property is present and the value is more than 1 => [dam:IndexedFragmentData] is used. Otherwise [dam:Asset].This property is set by a specific procedure which is described here:On...

Hello @aanchal-sikka I think you might need to reverse-engineer the AEM code to understand what is the differentiation logic  It can't be configured somehow.Also, I see that the query you are using is traversal, so I would recommend to:1. Follow this procedure https://experienceleague.adobe.com/docs...

Hello, I would add that you can configure the DEBUG logger for com.adobe.cq.dam.cfm.graphql.ContentFragmentsFetcher And there you can see the actual JCR query which is performed for your GraphQL query.

Answering my own question Tested the queries with a bit more data (4.5k content fragments) and results are the followingusing /oak:index/contentFragments the query has about 170ms execution time/oak:index/fragments has about 450msSo it's better to use contentFragments index.The solution for the back...

Hello, I'm using AEM 6.5.17 on-prem and have AEM Content Fragment with GraphQL Index Package 1.1.1 installed.This package has the following indexes: /oak:index/fragments { "jcr:primaryType": "oak:QueryIndexDefinition", "selectionPolicy": "tag", "compatVersion": 2, "includedPaths": [ "/co...

Hello everyone.I'm using AEM 6.5 on-premise and wondering why GraphQL persisted queries are not cached by default on the Dispatcher?In order to cache them, I need to add a .json extension to the request, because by default the request without extension is not cached.In the video, the procedure to up...

Hey @spidey1405 @rakesh_h  I'm having exactly the same issue, would be great if you can share more details if you resolved it. Thanks

Just additional info that the same issue reproduces for me on AEM 6.5.12, while on 6.5.15 it works fine. Anyways, the way to go is to use the provided solution.