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

AEM6.5 query throws exception even after oak indexing for OOTB query

Avatar

Avatar
Validate 25
Level 4
srinivas_chann1
Level 4

Likes

19 likes

Total Posts

222 posts

Correct Reply

6 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile

Avatar
Validate 25
Level 4
srinivas_chann1
Level 4

Likes

19 likes

Total Posts

222 posts

Correct Reply

6 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Ignite 5
Ignite 3
View profile
srinivas_chann1
Level 4

04-03-2021

Hi,

 

I was able to create oak  index based on the finding from https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem6-5-indexing-on-ootb-qu...

 

The query that is triggered is using

 http://localhost:4502/content/project/us/en.find.json?_charset_=utf-8&f=abc&cs=false&wwo=false&cq_ck=1614580151256

 

 

But when i execute command on the top content path  i.e /content/projectpath

select [jcr:path], [jcr:score], * from [nt:base] as a where isdescendantnode(a, '/content/projectpath/us/en') and lower([jcr:title]) like '%calling all%' union select [jcr:path], [jcr:score], * from [nt:base] as a where isdescendantnode(a, '/content/projectpath/us/en') and lower([jcr:description]) like '%calling all%' union select [jcr:path], [jcr:score], * from [nt:base] as a where isdescendantnode(a, '/content/projectpath/us/en') and lower([jcr:text]) like '%calling all%' union select [jcr:path], [jcr:score], * from [nt:base] as a where isdescendantnode(a, '/content/projectpath/us/en') and lower([text]) like '%calling all%' option(traversal OK)

 

 

Then it throws an exception ,how to solve this issue

 

 

Path for query 

/libs/granite/operations/content/diagnosistools/queryPerformance.html

 

srinivas_chann1_0-1614882172335.png

 

How to resolve this issue.

 

Thanks

View Entire Topic

Avatar

Avatar
Ignite 1
Level 4
davidjgonzalezzzz
Level 4

Likes

54 likes

Total Posts

60 posts

Correct Reply

20 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile

Avatar
Ignite 1
Level 4
davidjgonzalezzzz
Level 4

Likes

54 likes

Total Posts

60 posts

Correct Reply

20 solutions
Top badges earned
Ignite 1
Give Back 5
Give Back 3
Give Back 10
Give Back
View profile
davidjgonzalezzzz
Level 4

05-03-2021

Unfortunately that is a (very) sub-optimal query, and very hard to tailor a custem index for. A few major issues:

 

* Queries on nt:base, aka "everything"

* Lots of lowercase comparisons (i doubt any indexes are tailored for that property comparison)

* LIKEs with leading wildcards '%someterm....'

 

To be honest, I would log an issue with Support and see if they have recommendations and/or if they can escalate to Engineering to provide a performant OOTB index (or tweak the underlying query to be able to leverage a query).

 

I don't like adjusting the Traversal limit, since as mentioned increasing it can impact AEM performance, and also, remember that this is a global parameter, so other queries youre not thinking/are added in the future might start "enjoying" this higher limit, further impacting AEM performance.