Maximum fragment size consolidation parameter

[gatesn]

There's an example in the docs of how consolidation can somewhat approximate LSM trees.

It would be helpful when operating in such a mode (consolidating after every write) to define a maximum fragment size preventing overly expensive consolidation. More expensive / unbounded consolidation can then be run manually at another time.

[gatesn]

Also having a dry-run mode would be really useful to experiment with consolidation parameters

[stavrospapadopoulos]

Thanks for raising this, it is already in our roadmap.