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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Summit 2023 [19th to 23rd March, Las Vegas and Virtual] | Complete AEM Session & Lab list
SOLVED

\/oak:index for search component

Avatar

Level 6

Hi

 

i have developed the search component using query builder and now to search work efficiently what type of changes we need to make for /oak:index/cqPageLucene

 

Regards

Manikantha R

 

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hey @manikanthar1295 ,

When you fire a query to search content, copy that query and paste it in Query Performance Tool(/libs/granite/operations/content/diagnosistools/queryPerformance.html) and find out if any index has been used or not. If yes, then you probably need to add the path(if that's inside /content/yourProject) in included path and if you're searching for any specific property, you should add that too.

 

If you happen to see that your query is a traversal query and not using any index, consider creating a custom index definition using Oak Index Definition Generator(https://oakutils.appspot.com/generate/index).

 

So basically while searching the content in your repository you search:
1. a specific type of node(nt:base, nt:unstructured, cq:Page, etc)

2. under a specific path(/content/yourProject)

..

.. and so on

 

The idea here is to have an index(either custom or existing) that should take care of your query and not let it become a traversal one.

Thanks,

Bilal.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 6

Hey @manikanthar1295 ,

When you fire a query to search content, copy that query and paste it in Query Performance Tool(/libs/granite/operations/content/diagnosistools/queryPerformance.html) and find out if any index has been used or not. If yes, then you probably need to add the path(if that's inside /content/yourProject) in included path and if you're searching for any specific property, you should add that too.

 

If you happen to see that your query is a traversal query and not using any index, consider creating a custom index definition using Oak Index Definition Generator(https://oakutils.appspot.com/generate/index).

 

So basically while searching the content in your repository you search:
1. a specific type of node(nt:base, nt:unstructured, cq:Page, etc)

2. under a specific path(/content/yourProject)

..

.. and so on

 

The idea here is to have an index(either custom or existing) that should take care of your query and not let it become a traversal one.

Thanks,

Bilal.