Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix: follow naming convention for msq task engine (#13127) 

* fix: follow naming convention for msq task engine

* more fixes

* add back in experimental

* fix anchor
This commit is contained in:
317brian 2022-09-21 18:46:06 -07:00 committed by GitHub
parent 2f731f356e
commit 7fa35839c0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/multi-stage-query/api.md
View File

@ -202,7 +202,7 @@ Keep the following in mind when using the task API to view reports:
- The task report for an entire job is associated with the `query_controller` task. The `query_worker` tasks do not have - The task report for an entire job is associated with the `query_controller` task. The `query_worker` tasks do not have
their own reports; their information is incorporated into the controller report. their own reports; their information is incorporated into the controller report.
- The task report API may report `404 Not Found` temporarily while the task is in the process of starting up. - The task report API may report `404 Not Found` temporarily while the task is in the process of starting up.
- As an experimental feature, the SQL task engine supports running SELECT queries. SELECT query results are written into - As an experimental feature, the MSQ task engine supports running SELECT queries. SELECT query results are written into
the `multiStageQuery.payload.results.results` task report key as an array of arrays. The behavior and result format of plain the `multiStageQuery.payload.results.results` task report key as an array of arrays. The behavior and result format of plain
SELECT queries (without INSERT or REPLACE) is subject to change. SELECT queries (without INSERT or REPLACE) is subject to change.

2
docs/multi-stage-query/concepts.md
View File

@ -27,7 +27,7 @@ sidebar_label: "Key concepts"
> extension, new in Druid 24.0. Refer to the [ingestion methods](../ingestion/index.md#batch) table to determine which > extension, new in Druid 24.0. Refer to the [ingestion methods](../ingestion/index.md#batch) table to determine which
> ingestion method is right for you. > ingestion method is right for you.
## SQL task engine ## Multi-stage query task engine
The `druid-multi-stage-query` extension adds a multi-stage query (MSQ) task engine that executes SQL statements as batch The `druid-multi-stage-query` extension adds a multi-stage query (MSQ) task engine that executes SQL statements as batch
tasks in the indexing service, which execute on [Middle Managers](../design/architecture.md#druid-services). tasks in the indexing service, which execute on [Middle Managers](../design/architecture.md#druid-services).

4
docs/multi-stage-query/index.md
View File

@ -29,11 +29,11 @@ description: Introduces multi-stage query architecture and its task engine
> ingestion method is right for you. > ingestion method is right for you.
Apache Druid supports SQL-based ingestion using the bundled [`druid-multi-stage-query` extension](#load-the-extension). Apache Druid supports SQL-based ingestion using the bundled [`druid-multi-stage-query` extension](#load-the-extension).
This extension adds a [multi-stage query task engine for SQL](concepts.md#sql-task-engine) that allows running SQL This extension adds a [multi-stage query task engine for SQL](concepts.md#multi-stage-query-task-engine) that allows running SQL
[INSERT](concepts.md#insert) and [REPLACE](concepts.md#replace) statements as batch tasks. As an experimental feature, [INSERT](concepts.md#insert) and [REPLACE](concepts.md#replace) statements as batch tasks. As an experimental feature,
the task engine also supports running SELECT queries as batch tasks. the task engine also supports running SELECT queries as batch tasks.
Nearly all SELECT capabilities are available in the SQL task engine, with certain exceptions listed on the [Known Nearly all SELECT capabilities are available in the multi-stage query (MSQ) task engine, with certain exceptions listed on the [Known
issues](./known-issues.md#select) page. This allows great flexibility to apply transformations, filters, JOINs, issues](./known-issues.md#select) page. This allows great flexibility to apply transformations, filters, JOINs,
aggregations, and so on as part of `INSERT ... SELECT` and `REPLACE ... SELECT` statements. This also allows in-database aggregations, and so on as part of `INSERT ... SELECT` and `REPLACE ... SELECT` statements. This also allows in-database
transformation: creating new tables based on queries of other tables. transformation: creating new tables based on queries of other tables.