◆ Apache Cassandra

List all available Cassandra keyspaces

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 taskList all keyspaces in the Cassandra cluster and their respective replication strategies and…+
List all keyspaces in the Cassandra cluster and their respective replication strategies and factors.
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 provide a comprehensive list of all database keyspaces to the security team, include…+
Before I provide a comprehensive list of all database keyspaces to the security team, include details on which keyspaces contain sensitive customer data, and flag any that do not meet our standard encryption-at-rest requirements for review.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA new Cassandra node was just added to the cluster, but when I query it, it's not showing all…+
A new Cassandra node was added to the cluster, but it's not showing all expected keyspaces.
A new Cassandra node was just added to the cluster, but when I query it, it's not showing all the expected keyspaces that are present on other nodes. I'm afraid this indicates a replication issue or a misconfiguration that could lead to data inconsistencies. Is it more likely a network partition issue, or a problem with the new node's Cassandra configuration? What's the best next move to ensure data consistency across the cluster?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get requests from different teams asking for a current inventory of database…+
I frequently get requests from different teams asking for a current inventory of Cassandra keyspaces and their properties.
I frequently get requests from different teams asking for a current inventory of database keyspaces and their properties, taking time away from my core work. This manual process is inefficient and prone to errors. What habit should I change to automate or streamline the process of providing up-to-date keyspace information, so I can empower teams to self-serve without constant interruptions?
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.