Currently, you can manually set scanSegments to control the number of partitions to split the data into.
We could also provide a segmentSize setting which could be an alternative to scanSegments to control the partitioning. The benefits would be that the same configuration (e.g. segmentSize: 100) could be used with different tables and it would automatically compute an appropriate number of segments that fit the desired size. Whereas with scanSegments you have to adapt its value to every table you migrate (because you want to adjust the number of segments according to each table size).
Currently, you can manually set
scanSegmentsto control the number of partitions to split the data into.We could also provide a
segmentSizesetting which could be an alternative toscanSegmentsto control the partitioning. The benefits would be that the same configuration (e.g.segmentSize: 100) could be used with different tables and it would automatically compute an appropriate number of segments that fit the desired size. Whereas withscanSegmentsyou have to adapt its value to every table you migrate (because you want to adjust the number of segments according to each table size)._Originally posted by @julienrf in https://github.com/scylladb/scylla-migrator/pull/143#discussion_r1619045818_