An AEM Developer creates a custom OAK index for /content/mywebsite under /oak:index node. While testing the live site. It is found that the index is not being applied to any query within the website. Default Lucene indexes with high cost are being picked up by the AEM.
What is the most likely of the issue?
The custom OAK lucene index is missing evaluatePathRestrictions property and includedPaths property
The Custom OAK lucene index is missing evaluatePathRestrictions property and queryPaths property
The Custom Oak Lucene index must include boost property to rank it higher than default Lucene index
The custom OAK Lucene index must be replaced with OAK Lucene Property index
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
These two properties are essential for ensuring that your custom index is applied correctly to queries on the /content/mywebsite
path. So, my recommendation is:
The custom OAK lucene index is missing evaluatePathRestrictions property and includedPaths property
These two properties are essential for ensuring that your custom index is applied correctly to queries on the /content/mywebsite
path. So, my recommendation is:
The custom OAK lucene index is missing evaluatePathRestrictions property and includedPaths property
The most likely issue is that the custom OAK Lucene index is missing the evaluatePathRestrictions property and the includedPaths property. These properties are essential to ensure that the custom index is applied to the correct paths, like /content/mywebsite, and optimize query performance.
Views
Replies
Total Likes