p.limit doesn't seem to work in group queries | Community
Skip to main content
T
thomasm46556898
Level 2
October 15, 2021
Solved

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

  • October 15, 2021
  • 1 reply
  • 1004 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by thomasm46556898

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/

1 reply

T
thomasm46556898AuthorAccepted solution
Level 2
October 15, 2021

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/

    Terms & ConditionsAccessibility statement

    Loading footer...