◆ Apache Cassandra

Update large number of rows

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 taskUpdate the `status` column to 'inactive' for all rows in the `user_accounts` table where…+
Update the `status` column to 'inactive' for all rows in the `user_accounts` table where `last_login_date` is older than January 1, 2023. Ensure this operation is batched in reasonable chunks to avoid overwhelming the cluster, and confirm the update count matches our expectation.
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 update 5 million customer records in the `customer_data` table to reflect the new…+
Before I update 5 million customer records in the `customer_data` table to reflect the new `segment` value, analyze the current cluster load and suggest the optimal batch size and concurrency settings for this operation. Also, recommend a rollback strategy in case of unexpected issues during the update.
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'm running a large update on the `product_inventory` table to adjust prices for 10 million…+
A large update operation is causing high read latencies for critical services.
I'm running a large update on the `product_inventory` table to adjust prices for 10 million items, and now our e-commerce front end is reporting slow product page loads. The update is still running, and I'm afraid if I stop it, we'll have inconsistent pricing, but if I continue, we'll lose sales. I can't tell if it's the update itself causing contention, or if the cluster is just generally overloaded. What's the most likely cause, and what's the best immediate action to mitigate the impact on the front end without corrupting data?
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 we perform a large-scale data update, like correcting historical data or applying a…+
Large-scale data updates frequently cause performance degradation or unexpected cluster issues.
Every time we perform a large-scale data update, like correcting historical data or applying a new business rule across millions of rows, we inevitably run into performance bottlenecks or unexpected cluster behavior. We often react to these issues rather than preventing them. What habit should I change to better predict and proactively manage the impact of these large updates on cluster health and critical services?
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.