apache
Remove todo from SplitUtils
I'm proposing that we leave the code as-is. I don't know that there is a reliable way to determine what the splits should be given the information that we have in the tablet metadata. The todo suggested running tests and doing some compactions, etc. But I think that it's really going to be situation dependent. Users can apply iterators to perform aggregation, deletes, etc. at compaction time that could influence the split points greatly. I think the better option here is to document compactions should be run first to get more accurate split points.
@dlmarion - I'm not sure this would work but your comment about split points being situation dependent has me wondering if we should allow the calculation to be pluggable/configurable in some way so a user could tune it for their use case? It may not really work or be practical for a user to actually come up with a custom way to compute it so might just be best to leave it up to the system but figured I'd bring it up.
