◆ Apache Cassandra

Execute CQL through shell script

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 `update_user_status.cql` script against the `user_profiles` keyspace on the production…+
Run the `update_user_status.cql` script against the `user_profiles` keyspace on the production cluster. Log all output to a file named `status_update_prod_20240726.log`.
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 run `update_user_status.cql` on production, verify that the script is idempotent and…+
Before I run `update_user_status.cql` on production, verify that the script is idempotent and won't cause data corruption if run multiple times. Also, confirm the expected number of rows it should affect, if possible, so I can cross-check after execution.
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 `update_user_status.cql` on production, and the script finished without errors, but…+
I just ran `update_user_status.cql` on production, and the script finished without errors, but the user statuses haven't changed.
I just ran `update_user_status.cql` on production, and the script finished without errors, but when I query the `user_profiles` table, the user statuses haven't changed. I'm afraid I targeted the wrong keyspace, or maybe the script had a silent failure. What's the immediate diagnostic step to confirm if the script actually connected and executed against the correct data, and what's the safest way to re-run it if needed?
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 CQL scripts that seem to succeed but don't produce the expected results, leading to…+
I often run CQL scripts that seem to succeed but don't produce the expected results, leading to confusion and re-work.
I often run CQL scripts that seem to succeed but don't produce the expected results, leading to confusion and re-work, especially when dealing with production data. It's hard to trust the output. What habit should I change to ensure I always have a robust way to verify script execution and its impact on the data, before declaring it complete?
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.