◆ Apache Cassandra

Archive and purge Cassandra data

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskArchive all data older than two years from the 'audit_logs' keyspace in the staging Cassandra…+
Archive all data older than two years from the 'audit_logs' keyspace in the staging Cassandra cluster.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the end of the quarter, develop a plan to archive and purge 'event_stream' data older…+
Before the end of the quarter, develop a plan to archive and purge 'event_stream' data older than 90 days from the production Cassandra cluster. Consider the impact on active queries and storage reduction, and suggest a schedule that minimizes disruption for the data science team.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur Cassandra cluster's disk usage is at 90%, and we're getting alerts. We have large amounts…+
Our Cassandra disk usage is critically high, and we need to free up space immediately.
Our Cassandra cluster's disk usage is at 90%, and we're getting alerts. We have large amounts of historical 'metrics_data' that can be purged, but I'm unsure of the safest way to do this without causing performance degradation or data inconsistencies during the process. What's the quickest way to free up significant space, and what are the immediate risks I need to watch out for while purging live data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself reacting to high database disk usage alerts, leading to rushed,…+
I'm constantly reacting to growing disk usage instead of managing it proactively.
I frequently find myself reacting to high database disk usage alerts, leading to rushed, stressful data purging operations. This reactive approach often means we're close to capacity, risking outages. What habit can I cultivate to proactively manage data retention and purging, ensuring we maintain healthy disk space without last-minute emergencies or impacting our data consumers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Cassandra's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.