SplitUtils consistently misnames min as maxCombinedSplitSize

[gerashegalov]

the logic in SplitUtils#getCombinedSplits clearly treats maxCombinedSplitSize as the min, and the actual split size may well exceed it.

[isnotinvain]

I guess it's poorly named, I think it's more like "target split size, but you may go over it if the last split to be combined is bigger" or something like that, right?

[dvryaboy]

Last split might be smaller, too.

[gerashegalov]

@dvryaboy correct, the last split can be smaller.

[gerashegalov]

@dvryaboy @isnotinvain max and min can in theory be both targets. In most situations but a small single split, we keep piling up on a single split as long as we have not reached the min target. Would minTargetSize work to clarify that normally it's a lower bound?