◆ Elasticsearch

Update specific field values

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 taskUpdate the 'status' field to 'resolved' for all documents in the 'log-2023-10-26' index where…+
Update the 'status' field to 'resolved' for all documents in the 'log-2023-10-26' index where the 'error_code' is '500' and the 'service_name' is 'payment-gateway'.
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 update the 'priority' field for these 1500 incidents, help me ensure I'm not…+
Before I update the 'priority' field for these 1500 incidents, help me ensure I'm not overlooking any dependencies or downstream systems that might rely on the current priority values for reporting or automated workflows. What checks should I run to confirm this update won't break anything or cause unexpected side effects?
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 updated a batch of user profiles to normalize their 'country' field, but now some users…+
I just updated a batch of user profiles, but now some users are reporting missing data.
I just updated a batch of user profiles to normalize their 'country' field, but now some users are reporting missing data in other fields. I'm afraid I might have accidentally overwritten more than I intended, and I can't tell which users are affected or what data is lost. What's the most reliable way to identify the scope of the problem and potentially revert the changes for those specific users without affecting others?
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 need to make bulk updates to data, and I'm always nervous about making a mistake…+
I frequently need to make bulk updates to data, and I'm always nervous about making a mistake.
I frequently need to make bulk updates to data, and I'm always nervous about making a mistake that could corrupt production. I often double-check my scripts multiple times, which is time-consuming. What habit can I change in my preparation or execution workflow to build more confidence and reduce the risk of errors when performing these critical updates?
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.