Question about hybrid filtering option | Community
Skip to main content
K
Karthikyarru
October 20, 2023
Solved

Question about hybrid filtering option

  • October 20, 2023
  • 3 replies
  • 1403 views

I came across this option about AEM GraphQL hybrid filtering which combines both JCR filtering with AEM filtering. In this documentation: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/headless/graphql-api/graphql-optimization.html?lang=en#use-aem-graphql-hybrid-filtering
It was explained that entire load will be split between JCR and AEM graphql. I came to know that JCR filter has few limitations, where it does not work today, like case-insensitivity, null-check, contains not etc

In this session, the same was explained: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/adobe-developers-live-may-2023-understand-graphql-api/td-p/591126

 

However, the query showed in the session is like normal graphql query. It does not show any differentiation between JCR and AEM graphql filterings. I want to check how it actually works like how the JCR query will be setup and how the results will be provided according to the query written. How it will be different from regular graphql query. It would be great if any kind of documentation is provided which explains this part. 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by jasghar

    Re:  ... I want to check how it actually works like how the JCR query will be setup and how the results will be provided according to the query written. How it will be different from regular graphql query. It would be great if any kind of documentation is provided which explains this part. 

     

    Linking to my reply on a relevant thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/adobe-developers-live-may-2023-understand-graphql-api/m-p/628910/highlight/true#M42070

     

    3 replies

    Nikita_Mitroshin
    Nikita_Mitroshin
    Level 2
    October 20, 2023

    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.

      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity Advisor
      Community Advisor
      October 20, 2023

      Hello @nikita_mitroshin 

       

      Thanks for sharing the information. As suggested, we have configured the logger and the output is:

       

      Queries executed from wknd-shared project:

      - adventures-by-activity

      SELECT main.* FROM [dam:Asset] AS main WHERE ISDESCENDANTNODE(main, '/content/dam') AND main.[jcr:content/contentFragment] = true AND main.[jcr:content/data/cq:model] = '/conf/wknd-shared/settings/dam/cfm/models/adventure' AND (([jcr:primaryType] IS NOT NULL)) ORDER BY main.[jcr:content/data/master/title] OPTION (INDEX TAG[fragments], TRAVERSAL FAIL)

      - adventures-by-slug

      SELECT main.* FROM [dam:Asset] AS main WHERE ISDESCENDANTNODE(main, '/content/dam') AND main.[jcr:content/contentFragment] = true AND main.[jcr:content/data/cq:model] = '/conf/wknd-shared/settings/dam/cfm/models/adventure' AND ((main.[jcr:content/data/*/slug] = 'bali-surf-camp')) ORDER BY main.[jcr:path] OPTION (INDEX TAG[fragments], TRAVERSAL FAIL)

       

      Need some help to understand: how do we differentiate what part of GraphQL query is executed as a JCR-filter and graphQL filter?

      Please suggest.

       

      Aanchal Sikka
        Nikita_Mitroshin
        Nikita_Mitroshin
        Level 2
        October 20, 2023

        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/experience-manager-65/developing/headless/delivery-api/graphql-optimized-filtering-content-update.html?lang=en

        2. After that, install this package with the suggested indexes for GraphQL

         

        Here I've shared some numbers of the tests I did with these indexes https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-v6-5-17-and-graphql-indexes-v1-1-1-fragments-vs/m-p/620420#M405

        So once you have it you should see that even with the filters in the GraphQL queries, the  JCR queries should perform pretty fast.

          jasghar
          Adobe Employee
          jasgharAdobe EmployeeAccepted solution
          Adobe Employee
          October 25, 2023

          Re:  ... I want to check how it actually works like how the JCR query will be setup and how the results will be provided according to the query written. How it will be different from regular graphql query. It would be great if any kind of documentation is provided which explains this part. 

           

          Linking to my reply on a relevant thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/adobe-developers-live-may-2023-understand-graphql-api/m-p/628910/highlight/true#M42070

           
            Terms & ConditionsAccessibility statement

            Loading footer...