[OAK-8967] OR query with ORDER BY don't work as expected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.22.3, 1.30.0, 1.8.25
• Component/s: indexing, search
• Assignee: Mohit Kataria
• Reporter: Mohit Kataria
• Created: 24/Mar/20 05:27
• Updated: 21/Oct/21 12:35
• Resolved: 25/Mar/20 14:37

Description

A query with Or and having order by along with limit Don't reproduce results as per order mentioned. 

e.g. 

Let content be:

"/UnionQueryTest1/node0",
"/UnionQueryTest/node0",
"/UnionQueryTest1/node0/node1",
"/UnionQueryTest/node0/node1",
"/UnionQueryTest1/node0/node1/node2",
"/UnionQueryTest/node0/node1/node2",
"/UnionQueryTest1/node0/node1/node2/node3",
"/UnionQueryTest/node0/node1/node2/node3"

each node having x = number in node name.

SELECT idn1.* FROM [nt:base] as idn1 WHERE ISDESCENDANTNODE([/UnionQueryTest]) OR  ISDESCENDANTNODE([/UnionQueryTest1]) ORDER BY idn1.[x] ASC

 

result should be  same as above mentioned where as current result come out to be

/UnionQueryTest1/node0
/UnionQueryTest1/node0/node1
/UnionQueryTest1/node0/node1/node2
/UnionQueryTest1/node0/node1/node2/node3
/UnionQueryTest1/node0/node1/node2/node3/node4
/UnionQueryTest/node0
/UnionQueryTest/node0/node1
/UnionQueryTest/node0/node1/node2

 

Issue Links

• links to: GitHub Pull Request #397