◆ Apache Cassandra

Load data in bulk into Cassandra

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 taskLoad the customer order history CSV from the S3 bucket 'my-company-data' into the 'orders'…+
Load the customer order history CSV from the S3 bucket 'my-company-data' into the 'orders' table in the 'customer_360' keyspace by Friday, ensuring the data types match the schema and handling any existing primary key conflicts by overwriting.
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 loading the new Q3 sales data into the database, review the current schema for the…+
Before loading the new Q3 sales data into the database, review the current schema for the 'sales_transactions' table. Suggest any indexing improvements or denormalization strategies that would optimize query performance for daily sales reports and real-time inventory checks.
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 user activity dashboard is showing data from yesterday, even though the ETL job for…+
The new analytics dashboard is showing stale data for user activity, but the daily ETL job reported success.
The user activity dashboard is showing data from yesterday, even though the ETL job for 'user_events' table completed successfully an hour ago. I'm afraid we're missing critical real-time insights for the marketing team's campaign launch this afternoon. I can't tell if it's a replication lag issue or if the data isn't even making it into the cluster. What's the most likely cause, and how should I start investigating without impacting production reads?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing credibility with the product team because new features often hit performance…+
I frequently find myself scrambling to optimize queries after new features go live, leading to performance bottlenecks.
I keep losing credibility with the product team because new features often hit performance walls in the database after deployment. I'm always reacting to slow queries. What habit should I change in my development workflow to proactively design for the database's query patterns and avoid these post-launch fire drills?
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.