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

docs: clarify native batch ingestion w/ overlapping segments (#8720) 

I was confused by a paragraph in the docs that I myself wrote!
This commit is contained in:
David Glasser 2019-10-22 21:01:56 -07:00 committed by Fangjin Yang
parent 2ab43aa688
commit b453fda251
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/ingestion/native-batch.md
View File

@ -81,10 +81,11 @@ You may want to consider the below things:
- The number of concurrent tasks run in parallel ingestion is determined by `maxNumConcurrentSubTasks` in the `tuningConfig`.
The supervisor task checks the number of current running sub tasks and creates more if it's smaller than `maxNumConcurrentSubTasks` no matter how many task slots are currently available.
This may affect to other ingestion performance. See the below [Capacity Planning](#capacity-planning) section for more details.
- By default, batch ingestion replaces all data in any segment that it writes to. If you'd like to add to the segment
instead, set the `appendToExisting` flag in `ioConfig`. Note that it only replaces data in segments where it actively adds
data: if there are segments in your `granularitySpec`'s intervals that have no data written by this task, they will be
left alone.
- By default, batch ingestion replaces all data (in your `granularitySpec`'s intervals) in any segment that it writes to.
If you'd like to add to the segment instead, set the `appendToExisting` flag in `ioConfig`. Note that it only replaces
data in segments where it actively adds data: if there are segments in your `granularitySpec`'s intervals that have
no data written by this task, they will be left alone. If any existing segments partially overlap with the
`granularitySpec`'s intervals, the portion of those segments outside the new segments' intervals will still be visible.
### Task syntax