◆ Elasticsearch

Delete all documents from index

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 delete all documents from the 'test-data-cleanup' index in the staging environment.…+
I need to delete all documents from the 'test-data-cleanup' index in the staging environment. This is for the QA team, so they can start fresh with their new test suite. Make sure it's completely empty when you're done.
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 delete all documents from the 'old-user-sessions' index in production, can you help me…+
Before I delete all documents from the 'old-user-sessions' index in production, can you help me confirm this is safe? I need to ensure no critical data will be lost. Show me the index's current size, the last time it was written to, and any dependencies it might have, then propose the command to delete everything.
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 data retention policy for the 'temp-logs' index just changed, and now we need to delete all…+
The data retention policy for the 'temp-logs' index just changed, and now we need to delete all documents older than 30 days, but I'm not sure if there's an existing snapshot policy that might conflict.
The data retention policy for the 'temp-logs' index just changed, and now we need to delete all documents older than 30 days. I'm afraid of accidentally deleting data that's still needed for compliance or that might be part of an active snapshot. The compliance officer will be reviewing this next week. What's the safest way to delete only the old documents without impacting recent data or breaking existing backups?
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 delete documents from various indices, often with specific criteria like…+
I frequently need to delete documents from various indices, often with specific criteria.
I frequently need to delete documents from various indices, often with specific criteria like age or status, and I'm always double-checking the query to avoid accidental data loss. This constant anxiety is slowing me down. What habit should I change to build more confidence and accuracy in my delete operations, especially when dealing with production data?
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.