◆ Apache Cassandra

Clean up large scale 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.

2prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore I run the `archive_old_logs.py` script on the `logs_archive` cluster, help me optimize…+
Before I run the `archive_old_logs.py` script on the `logs_archive` cluster, help me optimize its performance and minimize impact. Suggest ways to batch deletions, tune consistency levels for cleanup, or identify potential hotspots that could cause performance degradation during the operation.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentThe data cleanup script I'm running on the `user_sessions` keyspace is taking hours longer than…+
The data cleanup script for `user_sessions` is running much slower than expected and causing high latency.
The data cleanup script I'm running on the `user_sessions` keyspace is taking hours longer than expected and `user_sessions` service latency is spiking. I'm afraid it's causing a major performance hit on the live application and might even lead to a timeout. I can't tell if it's the query itself, the cluster load, or a compaction issue. What's the likely diagnosis, and what's the best next move to either speed it up or safely pause it without corrupting data?
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.