◆ Apache Cassandra

Alter composite primary key in Cassandra

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
See the prompt↓All Apache Cassandra tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to add 'region' as a clustering key to the primary key of the 'user_sessions' table,…+
I need to add 'region' as a clustering key to the primary key of the 'user_sessions' table, after 'session_id', to improve query performance.
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 launch the new user activity tracking feature, I need to make sure the 'activity_log'…+
Before we launch the new user activity tracking feature, I need to make sure the 'activity_log' table's primary key supports efficient queries by user, by date, and by activity type. I suspect the current primary key isn't optimal for all these access patterns and might lead to hot partitions.
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 product team needs to query the 'event_data' table by a new field, 'event_category', which…+
The product team wants to add a new query pattern on an existing table, and it requires changing the primary key, but the table is already in production with billions of rows.
The product team needs to query the 'event_data' table by a new field, 'event_category', which isn't part of the current primary key. This table has billions of rows in production. I'm afraid of the downtime and data migration complexity if I alter the primary key, and I can't tell if there's a less disruptive way to support this new query. What's the safest and most efficient path forward to accommodate this new access pattern without impacting live users?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly facing the difficult and risky task of altering primary keys on massive…+
We frequently find ourselves needing to alter primary keys on large production tables due to evolving query patterns.
I'm constantly facing the difficult and risky task of altering primary keys on massive production tables because new query patterns emerge. This process is time-consuming and carries significant risk of downtime or data loss. What habit should I change in our data modeling and requirements gathering process to anticipate future access patterns better and design more flexible primary keys from the start, avoiding these painful 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.