This message was deleted.

This gets generated for Native batch ingestion tasks not specific to compaction: From guide:

In the partial segment generation phase, just like the Map phase in MapReduce, the Parallel task splits the input data based on the split hint spec and assigns each split to a worker task. Each worker task (type partial_index_generate) reads the assigned split,

The partial segment merge phase is similar to the Reduce phase in MapReduce. The Parallel task spawns a new set of worker tasks (type partial_index_generic_merge) to merge the partitioned data created in the previous phase.

https://druid.apache.org/docs/latest/ingestion/native-batch.html

yeah in particular they could be subtasks of

compact

or

index_parallel

Thanks @Bibek Sahoo and @Gian Merlino !!! Is there a way to differentiate the

single_phase_sub_task

- like which one trigger due to

compact

or

index_parallel

? Looking to configure overlord dynamic config so that

compact

task are send to seperate tier ?