Expand my Community achievements bar.

Join us in celebrating the outstanding achievement of our AEM Community Member of the Year!
SOLVED

p.limit doesn't seem to work in group queries

Avatar

Level 2

Hi,

 

I'm trying to utilize the below AEM Query:

type=cq:Page
p.hits=selective
p.properties=jcr:path
p.limit=-1
1_group.1_daterange.property=jcr:content/cq:lastModified
1_group.1_daterange.upperBound=2021-10-14
1_group.2_nodename=gr*
1_group.2_property.comparison=like
path=/content/

But it returns everything under /content/ and ignores the second part of the group. However, if I used this query:


type=cq:Page
p.hits=selective
p.properties=jcr:path
1_group.1_daterange.property=jcr:content/cq:lastModified
1_group.1_daterange.upperBound=2021-10-14
1_group.2_nodename=gr*
1_group.2_property.comparison=like
path=/content/

It works as expected (except that its returning a subset of rows).

I'm not seeing anything in the documentation that suggest an alternative to use in this case. What am I doing wrong?

1 Accepted Solution

Avatar

Correct answer by
Level 2

I got this fixed. I removed the groups altogether and the query seems to work. This is what I used below:

 

type=cq:Page

p.hits=selective

p.limit=-1

p.properties=jcr:path

daterange.property=jcr:content/cq:lastModified

daterange.lowerBound=0

daterange.upperBound=2021-10-14

nodename=gr*

property.comparison=like

path=/content/

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

I got this fixed. I removed the groups altogether and the query seems to work. This is what I used below:

 

type=cq:Page

p.hits=selective

p.limit=-1

p.properties=jcr:path

daterange.property=jcr:content/cq:lastModified

daterange.lowerBound=0

daterange.upperBound=2021-10-14

nodename=gr*

property.comparison=like

path=/content/