mirror of
https://github.com/apache/druid.git
synced 2025-02-09 03:24:55 +00:00
d007477742
* Docusaurus build framework + ingestion doc refresh. * stick to npm instead of yarn * fix typos * restore some _bin * Adjustments. * detect and fix redirect anchors * update anchor lint * Web-console: remove specific column filters (#8343) * add clear filter * update tool kit * remove usless check * auto run * add % * Fix resource leak (#8337) * Fix resource leak * Patch comments * Enable Spotbugs NP_NONNULL_RETURN_VIOLATION (#8234) * Fixes from PR review. * Fix more anchors. * Preamble nix. * Fix more anchors, headers * clean up placeholder page * add to website lint to travis config * better broken link checking * travis fix * Fixed more broken links * better redirects * unfancy catch * fix LGTM error * link fixes * fix md issues * Addl fixes
1.9 KiB
1.9 KiB
| id | title |
|---|---|
| datasource | Datasources |
A data source is the Apache Druid (incubating) equivalent of a database table. However, a query can also masquerade as a data source, providing subquery-like functionality. Query data sources are currently supported only by GroupBy queries.
Table datasource
The table data source is the most common type. It's represented by a string, or by the full structure:
{
"type": "table",
"name": "<string_value>"
}
Union datasource
This data source unions two or more table data sources.
{
"type": "union",
"dataSources": ["<string_value1>", "<string_value2>", "<string_value3>", ... ]
}
Note that the data sources being unioned should have the same schema. Union Queries should be always sent to a Broker/Router process and are NOT supported directly by the Historical processes.
Query datasource
This is used for nested groupBys and is only currently supported for groupBys.
{
"type": "query",
"query": {
"type": "groupBy",
...
}
}