custom lucene index not used by query in AEMaaCS | Community
Skip to main content
A
ahli008
Level 2
October 18, 2023
Solved

custom lucene index not used by query in AEMaaCS

  • October 18, 2023
  • 3 replies
  • 1442 views

Hi community members,

 

I've created below custom oak:index in my local instance with aem-sdk 20230713T151945Z-230601.

 

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:tm="internal"
compatVersion="{Long}2"
async="async"
jcr:primaryType="oak:QueryIndexDefinition"
evaluatePathRestrictions="{Boolean}true"
type="lucene">
<indexRules jcr:primaryType="nt:unstructured">
<feedItem jcr:primaryType="nt:unstructured">
<properties jcr:primaryType="nt:unstructured">
<publishDate name="tm:publishDate" ordered="{Boolean}true" jcr:primaryType="nt:unstructured"/>
<isNotShown name="tm:doNotShow/tm:isNotShown" propertyIndex="{Boolean}true" jcr:primaryType="nt:unstructured"/>
</properties>
</feedItem>
</indexRules>
</jcr:root>

 

The index is created under /oak:index successfully. 

 

But when using queryPerformance to explain query:

/jcr:root/content/refdata/RssFeeds/ninecelebrity//element(*, tm:feedItem)[(tm:doNotShow/@tm:isNotShown = 'false')] order by @1598819:publishDate descending

 

It says "No indexes were used. This is a traversal query.".

 

Anybody has idea why the created index not used in the query?

 

Best Regards,

 

Eddie 

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

3 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
October 18, 2023

Please check
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/indexing.html?lang=en#preparing-the-new-index-definition

 

Arun Patidar
    A
    ahli008Author
    Level 2
    October 18, 2023

    Hi Arun,

     

    Thanks for your reply.

    The index has been named as mhp.news-1-custom-1 according to the naming pattern by Adobe. 

    <prefix>.<indexName>-<productVersion>-custom-<customVersion>

     

    Regards,

     

    Eddie

     

     

     

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

      Hello @ahli008 

       

      Once the index is redeployed, please check the error.log, if the indexing was completed.

      If in doubt, set reindex ="true" on the index, that should start the re-indexing.

       

      Also, please refer to /oak:index/damAssetLucene

      The type for a Date should look something like this:

       

      Please assure that the propertynames including the node is correct related to the Parent node that we are searching for.

       

       

       

      Aanchal Sikka
        A
        ahli008Author
        Level 2
        October 18, 2023

        Hi Anachal,

         

        Tested giving publishDate type attr of Date. Still no index were used.

         

        Regards,

         

        Eddie

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

          @ahli008 

           

          1. Was the indexing completed after the changes were made?
          2. Can you please share the node structure of  tm:feedItem along with the properties
          Aanchal Sikka
            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            October 19, 2023

            @ahli008 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...