Reindexing of /oak:index/cqAuditLucene is not working

Avatar

Avatar
Ignite 1
Level 1
viveka_S
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
View profile

Avatar
Ignite 1
Level 1
viveka_S
Level 1

Likes

0 likes

Total Posts

3 posts

Correct reply

0 solutions
Top badges earned
Ignite 1
View profile
viveka_S
Level 1

02-07-2021

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.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

566 likes

Total Posts

712 posts

Correct reply

236 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile

Avatar
Boost 500
MVP
Vijayalakshmi_S
MVP

Likes

566 likes

Total Posts

712 posts

Correct reply

236 solutions
Top badges earned
Boost 500
Give Back 50
Give Back 5
Ignite 10
Ignite 5
View profile
Vijayalakshmi_S
MVP

06-07-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

Answers (2)

Answers (2)

Avatar

Avatar
Contributor
Level 4
Bimmi_Soi
Level 4

Likes

68 likes

Total Posts

76 posts

Correct reply

24 solutions
Top badges earned
Contributor
Applaud 5
Boost 50
Ignite 1
Affirm 10
View profile

Avatar
Contributor
Level 4
Bimmi_Soi
Level 4

Likes

68 likes

Total Posts

76 posts

Correct reply

24 solutions
Top badges earned
Contributor
Applaud 5
Boost 50
Ignite 1
Affirm 10
View profile
Bimmi_Soi
Level 4

04-07-2021

Hi @viveka_S ,

 

Please try using below link.

 

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

 

Hope this helps!

 

Thanks

Avatar

Avatar
Affirm 100
MVP
shelly-goel
MVP

Likes

246 likes

Total Posts

409 posts

Correct reply

105 solutions
Top badges earned
Affirm 100
Give Back 25
Ignite 3
Give Back 10
Validate 1
View profile

Avatar
Affirm 100
MVP
shelly-goel
MVP

Likes

246 likes

Total Posts

409 posts

Correct reply

105 solutions
Top badges earned
Affirm 100
Give Back 25
Ignite 3
Give Back 10
Validate 1
View profile
shelly-goel
MVP

02-07-2021

@viveka_S  Try to keep either includedPaths or just excludedPaths