◆ Apache Cassandra

Automate Cassandra data compliance

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 taskGenerate a report of all Personally Identifiable Information (PII) fields across the…+
Generate a report of all Personally Identifiable Information (PII) fields across the `user_profiles` and `customer_support` keyspaces, due by end of day Tuesday for the legal team.
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 the audit next month, implement a process to automatically redact sensitive payment card…+
Before the audit next month, implement a process to automatically redact sensitive payment card information from the `transaction_details` table after 90 days, ensuring compliance with PCI DSS. Make sure the redaction is irreversible and auditable.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new data retention policy requires deleting customer data from the database after 7 years,…+
Our new data retention policy requires deleting customer data from Cassandra after 7 years, but some old tables don't have TTLs set correctly.
Our new data retention policy requires deleting customer data from the database after 7 years, but some old tables don't have Time To Live settings correctly. The compliance officer is asking for proof of deletion. I'm afraid of accidentally deleting data that's still needed, but manual identification is too slow. How can I safely identify and apply the correct Time To Live settings or perform targeted deletions without disrupting live services or violating the policy?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently discover new data compliance requirements after data models are already in…+
We frequently discover new data compliance requirements after data models are already in production.
We frequently discover new data compliance requirements after data models are already in production, leading to costly refactoring. This impacts our credibility with legal and security teams. What habit should I change to involve compliance considerations earlier in the data modeling and pipeline design process, so we build in data governance from the start?
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.