-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: blurb about msq union all #15223
Conversation
docs/querying/sql.md
Outdated
Keep the following in mind when writing top-level UNION ALL queries: | ||
|
||
- You can't apply GROUP BY, ORDER BY, or any other operator to the results of a UNION ALL. | ||
- If you use the MSQ task engine for the query, the SQL planner attempts to plan the top-level UNION ALL as a table-level UNION ALL. Because of this, the query behaves the same as a table-level UNION ALL, meaning it has the same characteristics and limitations. If the planner can't plan the query as a table-level UNION ALL, the query fails. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- If you use the MSQ task engine for the query, the SQL planner attempts to plan the top-level UNION ALL as a table-level UNION ALL. Because of this, the query behaves the same as a table-level UNION ALL, meaning it has the same characteristics and limitations. If the planner can't plan the query as a table-level UNION ALL, the query fails. | |
- If you use the MSQ task engine for the query, the SQL planner attempts to plan the top-level UNION ALL as a table-level UNION ALL. Therefore it has the same limitations as the table level union all - You can only union TableDataSources with simple projections - select columns and rename columns. Clauses like GROUP BY, ORDER BY, etc are not supported on operands of union. | |
The query isn't supported if the planner can't plan it as a table-level union all |
docs/querying/sql.md
Outdated
::: | ||
Keep the following in mind when writing top-level UNION ALL queries: | ||
|
||
- You can't apply GROUP BY, ORDER BY, or any other operator to the results of a UNION ALL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can coalesce into a single paragraph as mentioned in the other comment
- You can't apply GROUP BY, ORDER BY, or any other operator to the results of a UNION ALL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This limitation predates my changes and seems to apply to any query engine. So does it no longer apply to non-MSQ queries?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This limitation is still present, but as per the previous comment, we can make it cohesive by coalescing both of the limitations into one big para.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, if we want it in 1 paragraph, I'll need to rewrite the paragraph first. Starting with If you use the MSQ task engine for the query,
sets the reader up to think that the whole paragraph is only about the MSQ task engine limitations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
9ab4130 has the new paragraph
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit. Looks good, otherwise.
Co-authored-by: Katya Macedo <[email protected]>
(cherry picked from commit 8769541)
Description
Add a blurb about how MSQ treats UNION ALL queries
This PR has: