type=sling:Folder
daterange.property=jcr:created
daterange.lowerBound=2022-09-06T01:00:00.000
daterange.upperBound=2022-09-08T18:00:00.000
group.1_group.path=/content/dam
group.2_group.path=/content/dam/we-retail
group.p.or=true
p.limit=-1
How to add path.self=true in above query.
Solved! Go to Solution.
Views
Replies
Total Likes
This is a rule within AEM where a query will stop after traversing a certain amount of nodes.
There are 3 ways in which you can overcome this:
1. Add more identifiers to your query which will narrow it down and search for less nodes.
Example: sling:resourceType, fulltext etc.
Why this works is because there are indexes for many JCR properties which are provided within AEM OOTB.
If you don't have any other identifiers, then
2. You would need to create a custom index which will then decrease your query time and also not traverse through all these nodes.
Reference: https://helpx.adobe.com/in/experience-manager/kb/create-custom-oak-index.html
The third way (is not a recommended approach if you are planning to use this query in a PROD,STG environment ).
But, if you are using it as a one-time thing in your local instance,there is a way where you can change the number of nodes traversed.
3. In your /system/console/configMgr, change the number of in-memory limit.
Hi @akshaybhujbale,
type=sling:Folder
daterange.property=jcr:created
daterange.lowerBound=2022-09-06T01:00:00.000
daterange.upperBound=2022-09-08T18:00:00.000
group.1_group.path=/content/dam
group.1_group.path.self=true
group.2_group.path=/content/dam/we-retail
group.2_group.path.self=true
group.p.or=true
p.limit=-1
References
https://github.com/paulrohrbeck/aem-links/blob/master/querybuilder_cheatsheet.md
https://hashimkhan.in/2015/12/02/query-builder/
Hope this helps!!
Thanks
when I have tried with ur query getting above error.
This is a rule within AEM where a query will stop after traversing a certain amount of nodes.
There are 3 ways in which you can overcome this:
1. Add more identifiers to your query which will narrow it down and search for less nodes.
Example: sling:resourceType, fulltext etc.
Why this works is because there are indexes for many JCR properties which are provided within AEM OOTB.
If you don't have any other identifiers, then
2. You would need to create a custom index which will then decrease your query time and also not traverse through all these nodes.
Reference: https://helpx.adobe.com/in/experience-manager/kb/create-custom-oak-index.html
The third way (is not a recommended approach if you are planning to use this query in a PROD,STG environment ).
But, if you are using it as a one-time thing in your local instance,there is a way where you can change the number of nodes traversed.
3. In your /system/console/configMgr, change the number of in-memory limit.
Answered the same on your previous question as well :
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-add-multiple-paths-...
group.1_group.path.self=true group.2_group.path.self=true
also, cheatsheet references you can refer to :
[1]https://experienceleague.adobe.com/docs/experience-manager-65/assets/JCR_query_cheatsheet-v1.1.pdf?l...
[2] https://github.com/paulrohrbeck/aem-links/blob/master/querybuilder_cheatsheet.md
getting below error after adding
group.1_group.path.self=true group.2_group.path.self=true
HI @Bimmi_Soi
I don't want to search the text. I want to search the modified pages.
Can you try without self.true
And can you explain what is the scenario and why are you adding self.true for better understanding?
As self.true : If true searches the subtree including the main node given in path, if false searches the subtree only
HI @Bimmi_Soi
I want to include main node as well as child nodes