◆ Elasticsearch

Migrate Elasticsearch versions

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 taskWe need to migrate the 'product_catalog' index from our current version 7.17 to the new 8.10…+
We need to migrate the 'product_catalog' index from our current version 7.17 to the new 8.10 cluster. Set up a reindex-from-remote process, ensuring all mappings and settings are preserved.
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 start the migration of the 'customer_orders' index to the new cluster, analyze the…+
Before I start the migration of the 'customer_orders' index to the new cluster, analyze the current index for any deprecated settings or mappings that might cause issues with version 8.10. Flag anything that will break or perform poorly so I can address it pre-migration.
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 started migrating the 'user_sessions' index to the new cluster and it's failing with…+
I just started migrating the 'user_sessions' index and it's failing with 'mapper_parsing_exception' errors for a specific field.
I just started migrating the 'user_sessions' index to the new cluster and it's failing with 'mapper_parsing_exception' errors for the 'user_agent_string' field. Our customer service team relies heavily on this data for Friday's weekly report. I don't know if the field was remapped incorrectly or if the data itself is malformed in the old index. I'm afraid of corrupting the new index or losing critical historical data. What's the quickest way to diagnose the mapping issue and get this migration back on track before Friday?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI repeatedly face unexpected mapping or data type conflicts when migrating indices between…+
I repeatedly face unexpected mapping or data type conflicts when migrating indices between major versions.
I repeatedly face unexpected mapping or data type conflicts when migrating indices between major versions, leading to last-minute scrambles and service interruptions. This costs us significant downtime. What habit should I change to proactively identify and resolve these incompatibilities early in the migration planning, instead of discovering them during the actual reindex process?
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 Elasticsearch'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.