◆ Elasticsearch

Create Elasticsearch dumps to S3

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 taskCreate a dump of the 'customer-profiles' index and upload it to the 'prod-data-dumps' S3…+
Create a dump of the 'customer-profiles' index and upload it to the 'prod-data-dumps' S3 bucket. Name the file 'customer_profiles_20240726.json'.
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 create the dump for 'customer-profiles', we need to make sure the data is anonymized…+
Before I create the dump for 'customer-profiles', we need to make sure the data is anonymized for PII. The last dump accidentally included sensitive customer emails. Ensure all PII fields are masked or excluded before it goes to S3.
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 analytics team needs a fresh dump of the 'product-catalog' index for a critical sales…+
The analytics team needs a fresh dump of 'product-catalog' data for a critical report, but they just told me the last dump they got was missing key fields.
The analytics team needs a fresh dump of the 'product-catalog' index for a critical sales report due Monday, but they just told me the last dump I provided was missing crucial 'inventory_count' fields. I'm afraid I used the wrong query or that the index structure changed without my knowledge. What's the best way to verify all required fields are included in the dump before it goes to S3, and how can I quickly confirm the index schema hasn't unexpectedly changed?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe're constantly getting feedback from the analytics and data science teams that the data dumps…+
We frequently get feedback from consuming teams that our data dumps are incomplete or contain unexpected data, causing delays in their work.
We're constantly getting feedback from the analytics and data science teams that the data dumps we provide are either incomplete, contain unexpected data, or are missing critical fields, leading to significant delays in their projects. This back-and-forth is wasting everyone's time. What habit should I change in how I prepare or validate these dumps to ensure they consistently meet the consumers' exact needs?
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.