Reindexing of /oak:index/cqAuditLucene is not working | Community
Skip to main content
viveka_S
viveka_S
July 2, 2021
Solved

Reindexing of /oak:index/cqAuditLucene is not working

  • July 2, 2021
  • 4 replies
  • 1486 views

Hi Team,

 

We have installed acs-aem-commons-audit-log-oak-index-4.8.6.zip Package to create the Audit log index and to perform the audit Log search, upon directly installing the package the index is getting created properly as below

 

But the problem here is more number of nodes are getting traversed 

 

 

In order to avoid that we have added few properties to the /oak:index/cqAuditLucene as highlighted below 

But upon adding these properties the reindex is not getting generated for any nodes. 

 

Hence the Audit log search is not giving any results, Kindly suggest on this.

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 Vijayalakshmi_S

Hi @viveka_s,

I suggest to do the following 

  • Remove the newly added properties (retain the one that is available as part of the package) -> reindex
  • Add logger for Query related APIs as well. 
    • org.apache.jackrabbit.oak.query.QueryEngineImpl
      org.apache.jackrabbit.oak.query.SQL2Parser
      org.apache.jackrabbit.oak.query.QueryImpl
      com.day.cq.search
      org.apache.jackrabbit.oak.query
  • Test the audit log functionality. Use different content root and observe the search results.
    • In particular, check if you have any audit information under the path - /content/myProject as part of search results
    • Check the query executed for audit log search and the index used. (Cross check if this index is picked for query execution)

Node count on reindexing is not a warning or issue unlike query traversal warning. 

If you are able to retrieve search results/audit information for your /content/myProject - Then use index properties with respect to path according to each of its significance one by one. 

You can refer this blog for significance of each of lucene index properties if needed - https://myaemlearnings.blogspot.com/2020/05/lucene-index-in-aem-part-1.html

4 replies

shelly-goel
Adobe Employee
shelly-goelAdobe Employee
Adobe Employee
July 2, 2021

@viveka_s  Try to keep either includedPaths or just excludedPaths

    B
    Adobe Employee
    BimmiSoAdobe Employee
    Adobe Employee
    July 5, 2021

    Hi @viveka_s ,

     

    Please try using below link.

     

    https://helpx.adobe.com/experience-manager/kb/DisableIndexingPartOfContent.html

     

    Hope this helps!

     

    Thanks

      viveka_S
      viveka_SAuthor
      July 5, 2021
      Hi All,
      Vijayalakshmi_S
      Vijayalakshmi_SAccepted solution
      Level 10
      July 6, 2021

      Hi @viveka_s,

      I suggest to do the following 

      • Remove the newly added properties (retain the one that is available as part of the package) -> reindex
      • Add logger for Query related APIs as well. 
        • org.apache.jackrabbit.oak.query.QueryEngineImpl
          org.apache.jackrabbit.oak.query.SQL2Parser
          org.apache.jackrabbit.oak.query.QueryImpl
          com.day.cq.search
          org.apache.jackrabbit.oak.query
      • Test the audit log functionality. Use different content root and observe the search results.
        • In particular, check if you have any audit information under the path - /content/myProject as part of search results
        • Check the query executed for audit log search and the index used. (Cross check if this index is picked for query execution)

      Node count on reindexing is not a warning or issue unlike query traversal warning. 

      If you are able to retrieve search results/audit information for your /content/myProject - Then use index properties with respect to path according to each of its significance one by one. 

      You can refer this blog for significance of each of lucene index properties if needed - https://myaemlearnings.blogspot.com/2020/05/lucene-index-in-aem-part-1.html

        Terms & ConditionsAccessibility statement

        Loading footer...