◆ Elasticsearch

Query all records from Elasticsearch

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 taskQuery the 'customer_feedback' index to retrieve all documents where the 'sentiment' field is…+
Query the 'customer_feedback' index to retrieve all documents where the 'sentiment' field is 'negative' and the 'product_id' is 'P1001'. Export the results as a JSON file for the product manager by end of day.
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 query to the marketing team for their campaign analysis, make sure it's…+
Before I give this query to the marketing team for their campaign analysis, make sure it's optimized and won't put undue strain on the cluster. Review the query for the 'website_visits' index, specifically looking for inefficient aggregations or wildcard searches that could slow things down. Suggest improvements to make it run faster without missing any key data.
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 CEO just asked for a count of all unique visitors from yesterday, and my usual query on the…+
The CEO just asked for a count of all unique visitors from yesterday, and my usual query is timing out.
The CEO just asked for a count of all unique visitors from yesterday, and my usual query on the 'access_logs' index is timing out, even after several attempts. I'm worried about not getting the data in time and also about crashing the cluster. What's the likely reason for the timeout with a count query on a high-volume index, and what's the most efficient way to get that unique visitor count without causing further performance issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often struggle to write efficient queries for large datasets, leading to slow responses or…+
I often struggle to write efficient queries for large datasets, leading to slow responses or cluster strain.
I often struggle to write efficient queries for large datasets, leading to slow responses or cluster strain, especially when dealing with complex aggregations or full-text searches. It feels like I'm always guessing at the best approach. What habit could I change in how I construct or test my queries to consistently retrieve data faster and minimize the impact on our production Elasticsearch cluster?
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.