From e23fd41fa7ac64b49e0301492e4962bbdc7be93d Mon Sep 17 00:00:00 2001 From: Justin Borromeo Date: Fri, 5 Apr 2019 15:14:07 -0700 Subject: [PATCH] Update SQL doc for planning change (#7415) --- docs/content/querying/sql.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/content/querying/sql.md b/docs/content/querying/sql.md index f6b30416a0f..a9e781bbf51 100644 --- a/docs/content/querying/sql.md +++ b/docs/content/querying/sql.md @@ -324,9 +324,7 @@ converted to zeroes). ## Query execution -Queries without aggregations will use Druid's [Scan](scan-query.html) or [Select](select-query.html) native query types. -Scan is used whenever possible, as it is generally higher performance and more efficient than Select. However, Select -is used in one case: when the query includes an `ORDER BY __time`, since Scan does not have a sorting feature. +Queries without aggregations will use Druid's [Scan](scan-query.html) native query type. Aggregation queries (using GROUP BY, DISTINCT, or any aggregation functions) will use one of Druid's three native aggregation query types. Two (Timeseries and TopN) are specialized for specific types of aggregations, whereas the other