aem custom oak index | Community
Skip to main content
Y
Ynvs
Level 2
January 28, 2026
Solved

aem custom oak index

  • January 28, 2026
  • 3 replies
  • 56 views

Hi i created a collectionLucene under oak index for /content/dam/collections path now it's blocking deletion under the path /content/dam/ *  with the status missing for guid to remidiate this I deleted the node collectionLucene but now the navigation in assets is experiencing a performance delay for every action of moving through the folders and all. 

 

 

Best answer by vikasbharti

When you deleted /oak:index/collectionLucene you removed the index that AEM was using for collection-related queries under /content/dam/collections. That explains both symptoms:

  • Before: delete was “blocked” because the index definition/content was inconsistent (missing guid, etc.), so certain operations on /content/dam were failing.
  • After deletion: AEM no longer has a suitable index for those queries, so anything that browses or filters assets/collections is now falling back to traversal, which feels like a big slowdown.


    To move forward:

  1. Restore or recreate the collection index (for example, based on the standard damCollectionLucene-* definition for /content/dam/collections) instead of deleting it, and deploy it via code/package.
  2. Set reindex = true on the recreated index and let the async indexer finish.
  3. Use the explain query tool when browsing /content/dam/collections to confirm that the new index is picked instead of traversal. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/query-and-indexing-best-practices#explain-query

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 2, 2026

​@vikasbharti ​@mbartlett ​@Vishal_Anand ​@giuseppebaglio ​@PGURUKRISHNA ​@narendragandhi Tagging you to see if you might want to share any best practices or insights on this topic. Your expertise would be greatly appreciated, thank you!

Kautuk Sahni
V
Adobe Employee
vikasbhartiAdobe EmployeeAccepted solution
Adobe Employee
February 2, 2026

When you deleted /oak:index/collectionLucene you removed the index that AEM was using for collection-related queries under /content/dam/collections. That explains both symptoms:

  • Before: delete was “blocked” because the index definition/content was inconsistent (missing guid, etc.), so certain operations on /content/dam were failing.
  • After deletion: AEM no longer has a suitable index for those queries, so anything that browses or filters assets/collections is now falling back to traversal, which feels like a big slowdown.


    To move forward:

  1. Restore or recreate the collection index (for example, based on the standard damCollectionLucene-* definition for /content/dam/collections) instead of deleting it, and deploy it via code/package.
  2. Set reindex = true on the recreated index and let the async indexer finish.
  3. Use the explain query tool when browsing /content/dam/collections to confirm that the new index is picked instead of traversal. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/query-and-indexing-best-practices#explain-query
    Y
    YnvsAuthor
    Level 2
    February 2, 2026

    Hi ​@vikasbharti thank you for your advice, I have recreated the index and following the best practices it seems I have missed the query path property I have added it and seen that the index is still being picked up and the deletion issue is resolved, but the latency is still present, would like to hear your inputs on this scenario, my thoughts are now that I have used the querypaths the oak should not use my index for traversal and should be back to working as it did prev so it should be another reason for this behavior would that be a possibility?? 

    Y
    YnvsAuthor
    Level 2
    February 2, 2026

    /oak:index/damAssetLucene

     

    Type

     

    : lucene

     

    Async

     

    : true

     

    Async lane name : async

     

    Last indexed up to : 2026-02-02T11:44:01.2322

     

    Last updated time

     

    : 2026-01-30T11:14:56.2322

     

    Size

     

    : 1.6 GB

     

    Estimated entry count : 116241

     

    Index definition changed without reindexing

     

    "/refresh":null could this cause slowness

    giuseppebaglio
    giuseppebaglio
    Level 10
    February 2, 2026

    hi ​@Ynvs,

    first of all you should restore the lucene index deleted, as suggested by ​@vikasbharti, because it is very import for many DAM operations.

    Then if you’re AEM 6.5, to create your custom index, you can leverage Ensure Oak Index  which allows index definitions to be defined in a content package, and then safely translated to real Oak Indexes.

    If you’re using AEMasCS, you can have a look at the official guide Indexing best practices in AEM: guides users in creating custom indexes, customizing out-of-the-box (OOTB) indexes, and using tools to analyze and optimize indexes; you can even find an example of index leveraging the dam:Asset node type.

      Terms & ConditionsAccessibility statement

      Loading footer...