This is an automated email from the ASF dual-hosted git repository.
brile pushed a commit to branch 28.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/28.0.0 by this push:
new d8c2fdee784 [backport] docs: blurb about msq union all (#15294)
d8c2fdee784 is described below
commit d8c2fdee784380ce234abe5c20225735e7ba994e
Author: 317brian <[email protected]>
AuthorDate: Wed Nov 1 11:23:08 2023 -0700
[backport] docs: blurb about msq union all (#15294)
---
docs/querying/sql.md | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/docs/querying/sql.md b/docs/querying/sql.md
index 13259bdf404..ba61e923d4b 100644
--- a/docs/querying/sql.md
+++ b/docs/querying/sql.md
@@ -224,9 +224,7 @@ UNION ALL
SELECT COUNT(*) FROM tbl WHERE my_column = 'value2'
```
-:::info
- With top-level queries, you can't apply GROUP BY, ORDER BY, or any other
operator to the results of a UNION ALL.
-:::
+Certain limitations apply when you use a top-level UNION ALL. For all
top-level UNION ALL queries, you can't apply a GROUP BY, ORDER BY, or any other
operator to the results of the query. For any top-level UNION ALL that uses the
MSQ task engine, the SQL planner attempts to plan the top-level UNION ALL as a
table-level UNION ALL. Because of this, UNION ALL queries that use the MSQ task
engine always behave the same as table-level UNION ALL queries. They have the
same characteristics and [...]
### Table-level
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
