[GLUTEN-7028][CH][Part-8] Support one pipeline write for partition mergetree #7924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
(Fixes: #7028)
The following digram shows the current class hierarchy,
SparkPartitionedBaseSink
inherits from ch'sDB::PartitionedSink
The partition MergeTree in pipeline write looks like this, it squashes block before partitiion for whole input:
It differs from spark 3.3 which squashes block after partitiion for each partition, since parition is triggerd by JVM.
The new implemwentation is same as clickhouse.
How was this patch tested?
Using existed UTs