You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by cw...@apache.org on 2019/04/05 22:14:12 UTC

[incubator-druid] branch master updated: Update SQL doc for planning change (#7415)

This is an automated email from the ASF dual-hosted git repository.

cwylie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git


The following commit(s) were added to refs/heads/master by this push:
     new e23fd41  Update SQL doc for planning change (#7415)
e23fd41 is described below

commit e23fd41fa7ac64b49e0301492e4962bbdc7be93d
Author: Justin Borromeo <jb...@edu.uwaterloo.ca>
AuthorDate: Fri Apr 5 15:14:07 2019 -0700

    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 f6b3041..a9e781b 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


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org