◆ Apache Cassandra

Develop and test database modifications

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
See the prompt↓All Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAdd a new column 'last_login' of type timestamp to the 'users' table in the 'customer_data'…+
Add a new column 'last_login' of type timestamp to the 'users' table in the 'customer_data' keyspace.
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 deploy this new 'order_history' table modification, make sure it won't cause any…+
Before I deploy this new 'order_history' table modification, make sure it won't cause any downtime or data inconsistencies. Verify the schema changes are additive and won't block existing reads or writes, and suggest a safe deployment strategy for the production cluster.
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 tried to add a new 'currency_code' column to the 'transactions' table on the staging…+
I just tried to add a new column to the 'transactions' table and it failed with a schema disagreement error.
I just tried to add a new 'currency_code' column to the 'transactions' table on the staging environment and it failed with a schema disagreement error, even after a full node restart. The dev team needs this column for a critical feature release next Tuesday. I'm afraid of corrupting the schema or causing data loss if I force it. What's the root cause of this disagreement, and what's the safest way to resolve it and get the column added without risking our data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternDatabase modification deployments are often fraught with unexpected errors or require multiple…+
Database modification deployments are often fraught with unexpected errors or require multiple attempts.
Database modification deployments are often fraught with unexpected errors or require multiple attempts, especially on our largest clusters. This causes delays for features and stress for the whole team. What habit should I change in my development and testing process for schema changes to ensure smoother, more reliable deployments the first time?
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.