From @Bj0rnen on July 23, 2018 11:12
We only install one command, run, with cstar. Of course, it's the most versatile kind of command, but having some commands that do something more specific would showcase the intended way of using cstar (not just using cstar run all the time).
In theory there are lots of commands that could make sense, like nodetool cleanup, nodetool disableautocompaction, nodetool enableautocompaction, nodetool stop COMPACTION, nodetool flush, etc.
Not sure if we have to strike a balance here, not being too spammy with commands, or if more is simply better.
From @Bj0rnen on July 23, 2018 11:12
We only install one command,
run, with cstar. Of course, it's the most versatile kind of command, but having some commands that do something more specific would showcase the intended way of using cstar (not just usingcstar runall the time).In theory there are lots of commands that could make sense, like
nodetool cleanup,nodetool disableautocompaction,nodetool enableautocompaction,nodetool stop COMPACTION,nodetool flush, etc.Not sure if we have to strike a balance here, not being too spammy with commands, or if more is simply better.