Marios Trivyzas 3c73602524 SQL: Fix wrong results when sorting on aggregate (#43154) ... - Previously, when shorting on an aggregate function the bucket processing ended early when the explicit (LIMIT XXX) or the impliciti limit of 512 was reached. As a consequence, only a set of grouping buckets was processed and the results returned didn't reflect the global ordering. - Previously, the priority queue shorting method had an inverse comparison check and the final response from the priority queue was also returned in the inversed order because of the calls to the `pop()` method. Fixes: #42851 (cherry picked from commit 19909edcfdf5792b38c1363b07379783ebd0e6c4)		2019-06-13 21:59:20 +02:00
..
src/test/java/org/elasticsearch/xpack/sql/qa/single_node	SQL: Fix wrong results when sorting on aggregate (#43154)	2019-06-13 21:59:20 +02:00
build.gradle	SQL: Move qa directory into sql directory (#34496)	2018-10-30 14:54:15 -04:00