◆ Elasticsearch

Filter where a field does not exist

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 Elasticsearch tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to find all documents in the 'customer_feedback' index where the 'sentiment_score' field…+
I need to find all documents in the 'customer_feedback' index where the 'sentiment_score' field does not exist. The marketing team needs this list by the end of the day to identify feedback that needs manual review.
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 give this list to the compliance team, I need to filter the 'audit_logs' index to show…+
Before I give this list to the compliance team, I need to filter the 'audit_logs' index to show only records where the 'reviewer_id' field is missing, but also exclude any records that have a 'status' of 'pending'. They need a clean list of unassigned, unreviewed logs for their weekly report.
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 reporting dashboard is showing an unexpected number of 'unassigned' tasks from the…+
The reporting dashboard is showing an unexpected number of 'unassigned' tasks from the 'task_management' index, which should have a 'due_date' field.
The reporting dashboard is showing an unexpected number of 'unassigned' tasks from the 'task_management' index, which should have a 'due_date' field. I'm filtering for documents where 'due_date' does not exist, but the count is much higher than expected. I'm afraid there might be a data ingestion issue, or perhaps some tasks are being created without the field for a reason I don't know. How can I quickly diagnose if this is a data quality problem or a legitimate workflow exception?
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 identify documents missing critical fields across various indexes for data…+
I frequently need to identify documents missing critical fields across various indexes for data cleanup and reporting.
I frequently need to identify documents missing critical fields across various indexes for data cleanup and reporting, and it often feels like a reactive scramble. This leads to inconsistent data quality and delayed insights for our business teams. What habit should I change to proactively monitor and alert on documents where essential fields are missing, rather than waiting for a report to break?
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.