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

Oak Queries and Indexing | AEM Community Discussion

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,157 likes

Total Posts

6,247 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,157 likes

Total Posts

6,247 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

24-07-2020

BlogImage.jpg

Oak Queries and Indexing by Adobe Docs

Abstract

Introduction
Unlike Jackrabbit 2, Oak does not index content by default. Custom indexes need to be created when necessary, much like with traditional relational databases. If there is no index for a specific query, possibly many nodes will be traversed. The query may still work but probably be very slow.
If Oak encounters a query without an index, a WARN level log message is printed:
*WARN* Traversed 1000 nodes with filter Filter(query=select ...) consider creating an index or changing the query


Indexer types and cost calculation
The Apache Oak based backend allows different indexers to be plugged into the repository.
One indexer is the Property Index , for which the index definition is stored in the repository itself.
Implementations for Apache Lucene and Solr are also available by default, which both support fulltext indexing.
The Traversal Index is used if no other indexer is available. This means that the content is not indexed and content nodes are traversed to find matches to the query.

Read Full Blog

Oak Queries and Indexing

Q&A

Please use this thread to ask the related questions.

AEM AEMIBlogSeeding Experience Manager