Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Impala 2.0
-
None
-
None
Description
Consider this query from our test suite (top-n.test):
select c1, c3, m2 from ( select c1, c3, max(c2) m2 from ( select c1, c2, c3 from ( select int_col c1, tinyint_col c2, max(id) c3 from functional.alltypessmall group by 1, 2 order by 1,2 limit 5 ) x ) x2 group by c1, c3 limit 10 ) t where c1 > 0 order by 2, 1 desc limit 3
The expected results are:
+----+----+----+ | c1 | c3 | m2 | +----+----+----+ | 1 | 96 | 1 | | 2 | 97 | 2 | | 3 | 98 | 3 | +----+----+----+
When building ASAN and enabling partitioned aggregation the results are:
+----+----+----+ | c1 | c3 | m2 | +----+----+----+ | 4 | 99 | 4 | +----+----+----+
When building ASAN and disabling partitioned aggregation the results are correct.