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

pitfall when using combining input source (#13639)

This commit is contained in:
Victoria Lim 2023-01-25 12:50:19 -08:00 committed by GitHub
parent 706b8a0227
commit 00cee329bd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ingestion/native-batch-input-source.md
View File

@ -756,6 +756,8 @@ Use the Combining input source only if all the delegates are splittable and can
Similar to other input sources, the Combining input source supports a single `inputFormat`.
Delegate input sources that require an `inputFormat` must have the same format for input data.
If you include the [Druid input source](#druid-input-source), the timestamp column is stored in the `__time` field.
To correctly combine the data from the Druid input source with another source, ensure that other delegate input sources also store the timestamp column in `__time`.
|Property|Description|Required|
|--------|-----------|---------|
@ -797,4 +799,4 @@ Set this value in `maxNumConcurrentSubTasks` in `tuningConfig` based on the seco
- `range` or `single_dim` partitioning: greater than or equal to 1
- `hashed` or `dynamic` partitioning: greater than or equal to 2
For more information on the `maxNumConcurrentSubTasks` field, see [Implementation considerations](native-batch.md#implementation-considerations).
For more information on the `maxNumConcurrentSubTasks` field, see [Implementation considerations](native-batch.md#implementation-considerations).