◆ Elasticsearch

Import JSON file into 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 taskImport the 'new_product_catalog.json' file into the 'products' index. This needs to be done…+
Import the 'new_product_catalog.json' file into the 'products' index. This needs to be done before the marketing team's campaign goes live tomorrow morning.
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 import the 'customer_feedback_q3.json' file into the 'feedback' index, can you help me…+
Before I import the 'customer_feedback_q3.json' file into the 'feedback' index, can you help me validate it? I need to ensure data quality. Check for any missing 'customer_id' fields, identify documents where 'rating' is outside the 1-5 range, and suggest how to handle these bad records during the import, either by skipping or marking them.
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 received a large 'historical_transactions.json' file to import into the 'transactions'…+
I just received a large 'historical_transactions.json' file to import, but I'm not sure if the existing 'transactions' index schema can handle all the new fields.
I just received a large 'historical_transactions.json' file to import into the 'transactions' index. I'm afraid of schema conflicts and data loss if the new fields don't map correctly, and rolling back a failed import of this size would be a nightmare for the data team. The finance director needs this data available by Monday. What's the best way to preview the schema impact of this JSON file on the existing index and identify potential mapping issues before I attempt the full import?
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 import JSON files, and often encounter schema mismatches or malformed data,…+
I frequently import JSON files into Elasticsearch, and often encounter schema mismatches or malformed data.
I frequently import JSON files, and often encounter schema mismatches or malformed data, leading to failed imports or corrupted indices. This constant need to troubleshoot is a huge drain on my productivity. What habit should I change to proactively validate incoming JSON files and prepare the target index, so I can ensure smoother, more reliable imports every time?
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.