◆ Elasticsearch

Perform bulk edits

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 change the 'department' field from 'Sales' to 'Client Success' for all documents in…+
I need to change the 'department' field from 'Sales' to 'Client Success' for all documents in the 'employee_records' index where the 'region' is 'North America'.
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 perform this bulk edit to update employee departments, run a dry run and show me a…+
Before I perform this bulk edit to update employee departments, run a dry run and show me a sample of the documents that would be affected. Also, flag any documents where the 'status' field is 'inactive' so I can decide if they should be excluded.
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 ran a bulk update to correct a product ID across several indexes and the operation…+
I just ran a bulk update to correct a product ID across several indexes and the operation completed, but now users are reporting missing products.
I just ran a bulk update to correct a product ID across several indexes and the operation completed without errors, but now users are reporting missing products in the catalog. The marketing team needs accurate data for their campaign launching tomorrow. I'm afraid I might have accidentally deleted or corrupted documents instead of just updating the ID. I don't know how to quickly verify the scope of the change or if a rollback is necessary. What's the best next move to quickly assess the damage and restore data integrity?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep making mistakes in bulk edits due to complex query conditions or unexpected data…+
I keep making mistakes in bulk edits due to complex query conditions or unexpected data variations.
I keep making mistakes in bulk edits due to complex query conditions or unexpected data variations, leading to data inconsistencies that take days to fix. This erodes trust in our data. What habit should I change to rigorously validate my bulk edit queries and anticipate edge cases before executing them, ensuring I only affect the intended documents and avoid unintended consequences?
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.