◆ Apache Cassandra

Delete all data in Cassandra column family

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 taskI need to clear out all the old test data from the `user_sessions` table in the `analytics`…+
I need to clear out all the old test data from the `user_sessions` table in the `analytics` keyspace on the staging cluster before tomorrow's performance run. Make sure it's completely empty.
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 I clear the `user_sessions` table for the staging performance test, confirm the exact…+
Before I clear the `user_sessions` table for the staging performance test, confirm the exact keyspace and table names so I don't accidentally wipe production. Also, give me the command to quickly verify it's empty afterward.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just ran the TRUNCATE command on `user_sessions` on the staging cluster, but when I query it,…+
I just ran the TRUNCATE command on `user_sessions` but the table still shows data.
I just ran the TRUNCATE command on `user_sessions` on the staging cluster, but when I query it, I still see old records. I'm afraid I've got a replication issue or I'm hitting the wrong node. What's the most likely reason for this, and what's the quickest way to confirm the data is actually gone across the cluster before the performance team starts their tests in an hour?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep accidentally truncating the wrong table or keyspace, or thinking data is gone when it…+
I keep accidentally truncating the wrong table or keyspace, or thinking data is gone when it isn't.
I keep accidentally truncating the wrong table or keyspace, or thinking data is gone when it isn't, especially when jumping between environments. This costs us time and creates confusion. What habit should I change to ensure I always target the correct data and verify its removal across the cluster reliably, without relying on muscle memory that might be wrong?
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.