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:index for search component

Avatar

Avatar
Affirm 1
Level 3
manikanthar1295
Level 3

Likes

7 likes

Total Posts

83 posts

Correct Reply

1 solution
Top badges earned
Affirm 1
Validate 25
Give Back 10
Give Back 5
Give Back 3
View profile

Avatar
Affirm 1
Level 3
manikanthar1295
Level 3

Likes

7 likes

Total Posts

83 posts

Correct Reply

1 solution
Top badges earned
Affirm 1
Validate 25
Give Back 10
Give Back 5
Give Back 3
View profile
manikanthar1295
Level 3

24-05-2021

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

 

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Springboard
Level 4
bilal_ahmad
Level 4

Likes

66 likes

Total Posts

108 posts

Correct Reply

16 solutions
Top badges earned
Springboard
Validate 10
Validate 1
Ignite 1
Establish
View profile

Avatar
Springboard
Level 4
bilal_ahmad
Level 4

Likes

66 likes

Total Posts

108 posts

Correct Reply

16 solutions
Top badges earned
Springboard
Validate 10
Validate 1
Ignite 1
Establish
View profile
bilal_ahmad
Level 4

24-05-2021

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.