Reference search index definition | Community
Skip to main content
C
costyfax
Level 2
October 18, 2024
Solved

Reference search index definition

  • October 18, 2024
  • 2 replies
  • 483 views

Hi all,

I'm facing warn entries in my error.log due to a deprecated lucene index.

 

org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index is deprecated: /oak:index/lucene

 

Based on this doc https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/removal-generic-lucene-index for reference search AEM should provide a new index /oak:index/pathreference but I cannot find it on my instances.

Anyone faced the same issue?

Where I can find the pathreference index definition?

 

Thank you!

 

Fabio

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 EstebanBustamante

Hi,

 

The article and index you are referring to are intended for AEMaaCS. Which version of AEM are you using? The article mentions that Adobe has "updated" their implementations, meaning the index is no longer used by their code. If you are using AEMaaCS and encountering that error, it’s likely because some of your code is still trying to use that index as the default.

In any case, you have two options: you can either create a new index to satisfy the query you’re seeing in the logs, or you can apply the pathReference index that is used in AEMaaCS (which is also available in the local SDK).

 

Please also check that you have applied this as well: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes#known-issues-aem-sites-6521 

 

 

 

Hope this helps!

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
October 18, 2024

Hi,

 

The article and index you are referring to are intended for AEMaaCS. Which version of AEM are you using? The article mentions that Adobe has "updated" their implementations, meaning the index is no longer used by their code. If you are using AEMaaCS and encountering that error, it’s likely because some of your code is still trying to use that index as the default.

In any case, you have two options: you can either create a new index to satisfy the query you’re seeing in the logs, or you can apply the pathReference index that is used in AEMaaCS (which is also available in the local SDK).

 

Please also check that you have applied this as well: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes#known-issues-aem-sites-6521 

 

 

 

Hope this helps!

Esteban Bustamante
    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    November 5, 2024

    @costyfax Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...