[DRILL-3327] row_number function returns incorrect result when only order by clause is specified

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: Query Planning & Optimization
• Labels: window_function
• Assignee: Victoria Markman
• Reporter: Victoria Markman
• Created: 19/Jun/15 21:03
• Updated: 25/Jun/15 17:49
• Resolved: 25/Jun/15 17:30

Description

Queries returning wrong result:

select c_integer, row_number() over(order by c_integer) from j1 order by 2;
select c_integer, row_number() over(order by c_integer) from j1 order by 2 desc;
select c_integer, row_number() over(order by c_integer desc) from j1 order by 2;
select c_integer, row_number() over(order by c_integer desc) from j1 order by 2;
select c_integer, row_number() over(order by c_integer nulls first) from j1 order by c_integer nulls last,  row_number() over(order by c_integer nulls first);
select c_integer, row_number() over(order by c_integer nulls last) from j1 order by c_integer nulls first, row_number() over(order by c_integer nulls last);

In attached tar file (row_number_wrong_result.tar) you will find:

1. *.sql - file that contains query
2. *.res - expected result (generated from Postgres)
3. *.out - result returned by drill

Issue Links

• depends upon: DRILL-3345 TestWindowFrame fails to properly check cases involving multiple batches
• is duplicated by: DRILL-3358 CUME_DIST window function provides wrong result when only ORDER BY clause is specified