Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Reindexing of /oak:index/cqAuditLucene is not working

viveka_S
Level 1
Level 1

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

viveka_S_0-1625228739942.png

 

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

 

viveka_S_1-1625228819330.png

 

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

viveka_S_2-1625229152267.png

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

 

viveka_S_3-1625229353601.png

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

1 Accepted Solution
Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

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

View solution in original post

4 Replies
shelly-goel
Community Advisor
Community Advisor

@viveka_S  Try to keep either includedPaths or just excludedPaths

Vijayalakshmi_S
Correct answer by
Community Advisor
Community Advisor

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

View solution in original post