◆ Apache Cassandra

Delete all rows from Cassandra table

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 taskEmpty the 'temp_log_entries' table in the 'analytics' keyspace on the development cluster.…+
Empty the 'temp_log_entries' table in the 'analytics' keyspace on the development cluster. Confirm it's clear after the operation.
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 clearing the 'user_sessions' table on staging, check for any active sessions that might…+
Before clearing the 'user_sessions' table on staging, check for any active sessions that might still be using it, and provide a quick report on how many records will be deleted.
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 need to clear the 'customer_data' table in our QA environment for a new test run. I'm afraid…+
I need to clear a table, but I'm not sure if there are any dependent views or materialized views that will break.
I need to clear the 'customer_data' table in our QA environment for a new test run. I'm afraid of accidentally breaking a downstream report or materialized view that relies on this data, as happened last month. I don't know if there are any direct dependencies. What's the best way to ensure I don't cause cascading failures?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I need to delete data from a table, I get anxious about breaking something…+
Deleting data often causes unexpected issues with dependent systems or reports.
Every time I need to delete data from a table, I get anxious about breaking something downstream that I don't even know about. It feels like a minefield. What habit should I change to gain more confidence and prevent these recurring surprises when performing data deletions?
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.