Discrepancy counting descendant pages between CQL and REST

I have two sets of page hierarchies that look like this:
11%20PM
If I call the REST API wiki/rest/api/content/R1/descendant/page, or if I execute a CQL search with ancestor=R1 AND type IN ( page ) I get the pages One, Two, and Three back as expected.

If I move R2 to be an immediate child of R1, the same REST API call returns all expected pages. However, the same SQL search returns pages One, Two, Three, and R2; missing are Four, Five and Six.

Am I searching incorrectly, or do I have incorrect expectations? Or should this be considered a bug in the CQL search implementation?

3 Likes

Hi @TimPesce,

I think this is covered by a bug I previously reported, CONFCLOUD-71276, but let me know if you think it’s different.

Regards,
Dugald

4 Likes

Thank you @dmorrow - that does indeed cover it!

3 Likes