◆ Apache Cassandra

Run CQL files from cqlsh

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 taskRun the new schema.cql script against the production cluster using cqlsh, making sure it…+
Run the new schema.cql script against the production cluster using cqlsh, making sure it executes cleanly before Friday's deployment window.
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 running the schema update on staging, check the cql script for any commands that could…+
Before running the schema update on staging, check the cql script for any commands that could block writes or reads, and flag potential performance impacts for the morning stand-up.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe new schema.cql file has a 'CREATE TABLE IF NOT EXISTS' command. I'm worried it will lock…+
The last schema update caused a brief outage because a table was locked during creation.
The new schema.cql file has a 'CREATE TABLE IF NOT EXISTS' command. I'm worried it will lock the cluster again during execution, even though it's 'IF NOT EXISTS'. I can't risk another production impact. Should I run this directly or break it into smaller, safer operations? What's the safest next move?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep having issues with schema changes causing brief service interruptions or unexpected…+
Schema changes often lead to unexpected cluster behavior or brief service interruptions.
We keep having issues with schema changes causing brief service interruptions or unexpected cluster behavior. I'm losing confidence in our deployment process for CQL files. What habit should I change to make our schema updates consistently safer and more predictable for the team?
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.