◆ Apache Cassandra

Run analytics on Cassandra data

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 daily fraud detection analytics script on the transaction data for yesterday, making…+
Run the daily fraud detection analytics script on the transaction data for yesterday, making sure the results are output to the 'fraud_reports' table by 8 AM for the risk team to review.
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 the fraud detection analytics for the risk team, make sure the query is optimized…+
Before I run the fraud detection analytics for the risk team, make sure the query is optimized for speed and resource usage, flag any potential performance bottlenecks, and suggest alternatives if it's going to impact production latency.
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 daily fraud detection query against the Cassandra cluster just timed out for the third time…+
The daily fraud detection query is timing out again, and the risk team is asking for the report.
The daily fraud detection query against the Cassandra cluster just timed out for the third time this morning, and the risk team is already asking where their report is. I'm afraid this is going to delay our critical morning meeting. I can't tell them we're still debugging. Is this a data volume issue, or a cluster health problem? What's the fastest way to get them the data and diagnose the root cause without impacting other services?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur analytics queries are constantly hitting timeouts or taking too long, especially during…+
Our Cassandra analytics queries frequently time out or run too long, delaying critical business reports.
Our analytics queries are constantly hitting timeouts or taking too long, especially during peak hours, which delays critical business reports and frustrates the risk and finance teams. We keep patching individual queries, but it's not sustainable. What habit should I change in how we design or execute these analytical workloads to prevent future incidents and ensure timely data delivery?
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.