◆ Apache Cassandra

Migrate Cassandra to other databases

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 taskExport the 'product_catalog' keyspace from the Cassandra cluster to a set of CSV files,…+
Export the 'product_catalog' keyspace from the Cassandra cluster to a set of CSV files, ensuring all tables are included and data types are preserved for import into the new PostgreSQL database.
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 we finalize the migration of the 'user_profiles' keyspace from the NoSQL database to the…+
Before we finalize the migration of the 'user_profiles' keyspace from the NoSQL database to the new managed relational database, analyze the existing NoSQL schema. Identify any complex data structures like collections or user-defined types that might not map directly, and propose a denormalized relational schema that preserves data integrity and query performance for the new application's requirements.
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 new 'order_history' service, now on PostgreSQL, is seeing really slow queries after we…+
The new 'order_history' service, running on a relational database, is experiencing slow queries after migrating data from Cassandra, and the data team is blaming the migration quality.
The new 'order_history' service, now on PostgreSQL, is seeing really slow queries after we migrated the data from the NoSQL database. The data team is convinced the data is 'bad' or poorly structured in the new database, but I followed the mapping exactly. I'm afraid we missed some subtle access pattern or an implicit NoSQL behavior that doesn't translate well to a relational model, and the product manager is getting impatient. What's the most likely cause of this performance degradation and how can I quickly identify if it's a data issue or a query optimization problem in the new system?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe consistently underestimate the complexity and time required to migrate data from NoSQL…+
We consistently underestimate the complexity and time required to migrate data from Cassandra to other database technologies.
We consistently underestimate the complexity and time required to migrate data from NoSQL databases to other database technologies, leading to project delays and frustrated stakeholders. This often stems from unforeseen schema translation issues or performance mismatches. What habit should I change in our initial assessment and planning phases to more accurately scope and execute these cross-database migrations?
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.