One question on mergeRollup tasks - do they honor segment partitioning strategy? For example, I have setup segmentPrunerTypes with some dimension based partitioning. When merge rollup tasks produce the merged segment, will the merged segments contain data that honors the dimension based partitioning?

For custom partitioning enabled tables, merge/rollup tasks will try to pick the segments from the same partition at the best effort (we honor segments with 1 partition). If some segments have data from more than 1 partitions, we fall back to the original behavior.

Thanks

The merged segments will always honor the partitioning config

Is this documented @User @User? If not, would be good to add that