@daniel-strmecki yeah caching probably would be the last option for me. I am just curious to know why fulltext= "random text" and fulltext = " " take so much time difference. Both are using cqPageLuceneIndex in my case. Not sure I should add some extra parameters for empty string search

Above queries are already picking cqPageLuceneIndex also after adding type=cq:Page no major time difference is seen.

Hi All, We have below full text query which is used to find pages under certain hierarchy and also with specific type of resourceType. Sample query 1:fulltext=random textgroup.1_path=/content/us/engroup.2_path=/content/ca/engroup.p.or=trueproperty = jcr:content/sling:resourceTypeproperty.1_value = p...

Thanks @somen-sarkar for quick response, it sorting but still in group, first group of result is from /us/en since our 1st path in query is /us/en and then second group is considered which is /ca/en which is 2nd path in our query and that is sorted separately 0: /content/us/en/page1.html jcr:score =...

When we do query search, results are grouped based on paths. For example, if we have queried for paths /content/us/en & /content/ca/en , then results will have group of pages from /us/en and after that it will have group of pages from /ca/en. Even if we try to sort orderby=@jcr:score , sorting is do...

Yeah getting same issue, after query search, results are grouped based on paths. For example, if we are having queried for paths /content/us/en & /content/ca/en , then results will have group of pages from /us/en and after that it will have group of pages from /ca/en. Even if we try to sort orderby=...