Adobe Experience Manager AD0-E134 Question # 14 Topic 2 Discussion

The warning WARN* Traversed 1000 nodes with filter Filter (query=select…) indicates that the query is performing a traversal instead of using an index. This results in poor performance, especially when the client has a large number of nodes (e.g., more than 100,000).

To resolve this issue, you should create a custom Oak index for the custom page property. This ensures that the queries can leverage the index for efficient data retrieval.

Steps to create a custom Oak index:

Define the Oak Index:

Navigate to the /oak:index node in CRXDE Lite (http://localhost:4502/crx/de).

Create a new node of type oak:QueryIndexDefinition.

Configure the Index:

Set the properties of the new index node to define the indexing rules for the custom page property.

{

"jcr:primaryType": "oak:QueryIndexDefinition",

"type": "property",

"propertyNames": ["customPageProperty"],

"reindex": true,

"async": "async"

}

Deploy and Reindex:

Save the changes and initiate a reindexing process.

Ensure that the reindex flag is set to true for the newly created index.

Validate the Index:

Use the Index Manager or the AEM Web Console to validate that the new index is enabled and functioning correctly.

By creating a custom Oak index for the custom page property, the queries will be optimized to use the index, significantly improving the search performance and resolving the client's issue.

References:

Adobe Experience Manager - Oak Indexing

Apache Jackrabbit Oak - Indexing