Hi,
Can we make some schema adjustments to System.compaction_history table to
meet our needs?
For example : If there is no task execution, what about just recording 0
bytes_in, 0 bytes_out for this compaction history . Other status can be
placed in compaction_properties,
and you can even add a c
Thank you Maxim for summarizing it like this for better visibility of what
you are suggesting to contribute.
I am OK with that in general but:
1) The table should be limited in its size (I think the original patch you
had was already done with space-limitation in mind). Since we want to put
this
Hello everyone,
I still need a few more eyes on [1][2], but this time I'm going to try
and do some marketing for the feature I'm talking about, so...
We are trying to bridge the gap between the API that is called and the
compaction process that MAY or MAY NOT be called as a result, and make
user
Hello everyone,
I would like to gently ask for help in reviewing the following issue
that we've been facing for a while:
https://issues.apache.org/jira/browse/CASSANDRA-19760
When a cleanup command is called, the compaction process under the
hood is triggered accordingly. However, if there is not
