◆ Apache Cassandra

Import and export Cassandra schema

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 taskI need to get the schema for the `customer_data` keyspace from the development cluster and…+
I need to get the schema for the `customer_data` keyspace from the development cluster and apply it to the QA cluster. Export it to a file, then import it.
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 export the `customer_data` schema from dev to QA, check for any user-defined types or…+
Before I export the `customer_data` schema from dev to QA, check for any user-defined types or custom indexes that might not transfer cleanly. Highlight anything that needs manual intervention or could cause a conflict when importing.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just imported the `customer_data` schema from dev to QA, but when I check, some tables are…+
I just imported the `customer_data` schema to QA, but some tables are missing columns, and I'm seeing errors about UDTs.
I just imported the `customer_data` schema from dev to QA, but when I check, some tables are missing columns, and I'm getting errors about unknown user-defined types. I'm worried I missed a dependency or the export wasn't complete. What's the most common cause for partial schema imports like this, and what's the best way to diagnose exactly what went wrong and fix it without re-importing everything blindly?
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 run into issues with schema drift or incomplete schema transfers between…+
I frequently run into issues with schema drift or incomplete schema transfers between environments, causing deployment delays.
I frequently run into issues with schema drift or incomplete schema transfers between environments, causing deployment delays and frantic debugging. It feels like I'm always playing catch-up. What habit should I change to proactively manage schema consistency and ensure smooth, predictable transfers, especially when UDTs or new features are involved?
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.