[HIVE-4429] Nested ORDER BY produces incorrect result

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 0.9.0
• Component/s: Query Processor, SQL, UDF

Environment

Red Hat Linux VM with Hive 0.9 and Hadoop 2.0

• Assignee: Unassigned
• Reporter: Mihir Kulkarni
• Created: 27/Apr/13 00:19
• Updated: 27/Apr/13 04:02

Description

Nested ORDER BY clause doesn't honor the outer one in specific case.

The below query produces result which honors only the inner ORDER BY clause. (it produces only 1 MapRed job)

SELECT alias.b0 as d0, alias.b1 as d1
FROM
    (SELECT test.a0 as b0, test.a1 as b1 
    FROM test
    ORDER BY b1 ASC, b0 DESC) alias    
ORDER BY d0 ASC, d1 DESC;

---

On the other hand the query below honors the outer ORDER BY clause which produces the correct result. (it produces 2 MapRed jobs)

SELECT alias.b0 as d0, alias.b1 as d1
FROM
    (SELECT test.a0 as b0, test.a1 as b1 
    FROM test
    ORDER BY b1 ASC, b0 DESC) alias    
ORDER BY d0 DESC, d1 DESC;

---

Any other combination of nested ORDER BY clauses does produce the correct result.
Please see attachments for query, schema and Hive Commands for reprocase.