◆ Apache Cassandra

Execute Cassandra commands

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 taskExecute a full repair on the 'user_preferences' keyspace across all nodes and confirm…+
Execute a full repair on the 'user_preferences' keyspace across all nodes and confirm completion within the next two hours, reporting any unrepairable ranges.
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 audit next month, review the current state of all keyspaces. Suggest three specific…+
Before the audit next month, review the current state of all keyspaces. Suggest three specific commands or sequences of commands to verify data integrity and consistency across the entire cluster, providing clear output for an external auditor.
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 tried to drop a column from 'user_data', and now the table is showing errors on reads. I'm…+
I tried to drop a column from 'user_data', and now the table is showing errors on reads.
I tried to drop a column from 'user_data', and now the table is showing errors on reads. I'm afraid I corrupted the schema or lost data, and I don't know how to revert it safely. What's the most likely reason for these read errors after a schema change, and what's the best next move to restore the table to a stable, readable state without data loss?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often run commands reactively to fix immediate issues, sometimes causing unintended side…+
I often run commands reactively to fix immediate issues, sometimes causing unintended side effects.
I often run commands reactively to fix immediate issues, sometimes causing unintended side effects because I'm always just trying to put out fires. What habit should I change to proactively plan and validate command executions, especially for critical operations, to minimize unexpected problems and ensure predictable outcomes?
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.