loui_wentzel
Databricks Partner

Depending on your table, running optimize or similar, it might be compute-benificial to have few size-outlies that are bigger or smaller than the target is a better solution, rather than hardsetting all the partitions to a set value. It's simply information that the smallest and biggest partition is 19920357 and 43475356 respectively, and the target was 33554432.