Hi， We have some unclear points about the segment size estimate when merging multi-segments.
We find that the segment merge job still uses CubeStatsReader::getCuboidSizeMap to estimate the total size of the merged segment. From our understanding, when building a new segment, Kylin uses this way to estimate the total size is OK since no other info we can turn to. But in merging we may sum the table size of the segments to be merged, which should be more accurate. So why for this consideration? Su Qilong
