Thanks for the links. I wanted to avoid a major compaction somehow.
I see many JIRA issues on timestamps related to compaction/reads. So many
improvements have been proposed.
--
Ravi
On Thu, Oct 10, 2013 at 12:26 AM, Shahab Yunus wrote:
> Ahh, yes, 'compaction'. I blanked out while mentioning
Ahh, yes, 'compaction'. I blanked out while mentioning repair and cleanup.
That is in fact what needs to be done first and what I meant. Thanks
Robert.
Regards,
Shahab
On Wed, Oct 9, 2013 at 1:50 PM, Robert Coli wrote:
> On Wed, Oct 9, 2013 at 7:35 AM, Ravikumar Govindarajan <
> ravikumar.govi
On Wed, Oct 9, 2013 at 7:35 AM, Ravikumar Govindarajan <
ravikumar.govindara...@gmail.com> wrote:
> What is the quick way to delete old-data and at the same time make sure
> read [doesn't] churn through all deleted columns?
>
Use a database that isn't log structured?
But seriously, in 2.0 there'
I might be missing something obvious here but can't you afford (time-wise)
to run cleanup or repair after the deletion so that the deleted data is
gone? Assuming that your columns are time-based data?
Regards,
Shahab
On Wed, Oct 9, 2013 at 10:35 AM, Ravikumar Govindarajan <
ravikumar.govindara.
We have wide-rows accumulated in a cassandra CF and now changed our
app-side logic.
The application now only wants first 7 days of data from this CF.
What is the quick way to delete old-data and at the same time make sure
read does churn through all deleted columns?
Lets say I do the following