◆ Apache Cassandra

Update large numbers of rows reliably

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 'processed' for all orders in the 'orders' table where 'status'…+
Update the 'status' column to 'processed' for all orders in the 'orders' table where 'status' is currently 'pending' and 'order_date' is before October 1, 2023.
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 we run the batch update to mark all inactive user accounts as 'archived' in the 'users'…+
Before we run the batch update to mark all inactive user accounts as 'archived' in the 'users' table, design a strategy to ensure data consistency and minimize impact on the live system. Consider potential contention with ongoing writes and how to resume safely if the process is interrupted, while keeping the customer support team aware of the expected completion time.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're running a large-scale update to correct pricing errors across millions of rows in the…+
A large-scale update to correct pricing errors in the 'products' table is failing intermittently with timeout errors, and the business needs it done by end of day.
We're running a large-scale update to correct pricing errors across millions of rows in the 'products' table, and it's failing intermittently with timeout errors, especially during peak hours. The business needs these prices corrected by end of day Friday for an upcoming promotion, and I'm afraid we're overloading the cluster or hitting some internal NoSQL limit. What's the most likely reason for these timeouts and what's the safest, most efficient way to complete this update without causing a full outage?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternLarge batch updates in NoSQL databases are always a source of anxiety and often lead to…+
Large batch updates in Cassandra are always a source of anxiety and often lead to performance issues or partial failures.
Large batch updates in NoSQL databases are always a source of anxiety and often lead to performance issues or partial failures, forcing us into reactive fixes. This impacts our confidence in making significant data changes. What habit should I change when approaching large-scale row updates to ensure they are consistently reliable, performant, and less disruptive to our production systems?
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.