org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index is deprecated | Community
Skip to main content
Love_Sharma
Love_Sharma
Level 4
July 30, 2021
Solved

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

  • July 30, 2021
  • 3 replies
  • 5468 views

Hello Community,

 

We are seeing lot of warning in our publish instance (only) because of which CPU usage is going high.

30.07.2021 12:07:12.078 *WARN* org.apache.jackrabbit.oak.plugins.index.lucene.LucenePropertyIndex This index is deprecated: /oak:index/lucene; it is used for query Filter(query=select [jcr:path], [jcr:score], * from [nt:base] as a where contains(*, '"/content/xyz"') /* xpath: //*[jcr:contains(., '"/content/dam/abc"')] */ fullText="/content/dam/abc", path=*). Please change the query or the index definitions.

Looking at https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-referencesearch-outputslucenepropertyindex-this-index-is/qaq-p/392556 I appreciate if someone can confirm, this issue still exists in the product or resolved ? If resolved, we have SP 6.5.9 installed already. 

 

Appreciate any help.

 

Thanks

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 Love_Sharma

Thanks @joerghoh for the response.

For the visitors (having same problem), My code is calling tagManager.findTagsByTitle() and tagManager.findTagsByTitle() which triggers a query and I was having this issue.

 

Solution which fixed the issue is adding below indexes

/oak:index/cqTagLucene/indexRules/cq:Tag/properties/jcrTitle-en

/oak:index/cqTagLucene/indexRules/cq:Tag/properties/jcrTitle-fr

3 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
August 1, 2021

It falls back to the "default" index (/oak:index/lucene), which is deprecated (but not removed), one of the reasons being that it is typically quite large.

I would not attribute the high load directly to it, this typically has other factors (e.g. because you do this query in the context of rendering a page). 

if you see this message only on publish, check if the author has additional indexes which you don't have on publish. 

 

(A side note: This query is quite silly, because it says: Give me everything below /content/dam/abc, and you can achieve that much easier with a tree traversal.)

    Love_Sharma
    Love_SharmaAuthorAccepted solution
    Level 4
    August 4, 2021

    Thanks @joerghoh for the response.

    For the visitors (having same problem), My code is calling tagManager.findTagsByTitle() and tagManager.findTagsByTitle() which triggers a query and I was having this issue.

     

    Solution which fixed the issue is adding below indexes

    /oak:index/cqTagLucene/indexRules/cq:Tag/properties/jcrTitle-en

    /oak:index/cqTagLucene/indexRules/cq:Tag/properties/jcrTitle-fr

      Wells_Sri
      Wells_Sri
      Level 2
      January 8, 2024

      Hi, 

       

      I am also facing same issue, can you tell me where need to add those two indexes and how to do that. Thanks.

       

      Regards,

      Sridhar

      K
      Kristoffer_Neil_Marianode
      February 4, 2022

      I'm currently encountering same issue when testing searches on publisher using search.html?q=%26

      Terms & ConditionsAccessibility statement

      Loading footer...