mirror of https://github.com/apache/druid.git
Update datasources.md: Fix Documentation. (#13865)
Fixed documentation to clarify that union query cant be run over query datasources.
This commit is contained in:
parent
ca68fd93a6
commit
b26f1b4a5d
|
@ -233,7 +233,7 @@ FROM
|
|||
<!--END_DOCUSAURUS_CODE_TABS-->
|
||||
|
||||
Query datasources allow you to issue subqueries. In native queries, they can appear anywhere that accepts a
|
||||
`dataSource`. In SQL, they can appear in the following places, always surrounded by parentheses:
|
||||
`dataSource` (except underneath a `union`). In SQL, they can appear in the following places, always surrounded by parentheses:
|
||||
|
||||
- The FROM clause: `FROM (<subquery>)`.
|
||||
- As inputs to a JOIN: `<table-or-subquery-1> t1 INNER JOIN <table-or-subquery-2> t2 ON t1.<col1> = t2.<col2>`.
|
||||
|
@ -423,4 +423,4 @@ The `unnest` datasource uses the following syntax:
|
|||
* `dataSource.outputName`: The name you want to assign to the column that will contain the unnested values. You can replace the source column with the unnested column by specifying the source column's name or a new column by specifying a different name. Outputting it to a new column can help you verify that you get the results that you expect but isn't required.
|
||||
* `dataSource.allowList`: Optional. The subset of values you want to unnest.
|
||||
|
||||
To learn more about how to use the `unnest` datasource, see the [unnest tutorial](../tutorials/tutorial-unnest-datasource.md).
|
||||
To learn more about how to use the `unnest` datasource, see the [unnest tutorial](../tutorials/tutorial-unnest-datasource.md).
|
||||
|
|
Loading…
Reference in New Issue