◆ Elasticsearch

Bulk index JSON data

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 taskBulk index the attached `product_updates.json` file into the `products_catalog`…+
Bulk index the attached `product_updates.json` file into the `products_catalog` index.
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 bulk index `product_updates.json` into `products_catalog`, validate that the JSON…+
Before I bulk index `product_updates.json` into `products_catalog`, validate that the JSON structure matches the existing mapping for the index, and ensure the operation uses a reasonable batch size to avoid overwhelming the cluster. I need to get these updates in quickly without causing performance issues for the live catalog.
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'm trying to bulk index a new set of product data, `new_inventory.json`, but the index…+
I'm trying to bulk index a new set of product data, but the index operation keeps failing with 'mapper parsing exception'.
I'm trying to bulk index a new set of product data, `new_inventory.json`, but the index operation keeps failing with 'mapper parsing exception'. I'm afraid I'll corrupt the `inventory` index if I force it, and the product team needs these updates live by end of day. I can't tell which specific field is causing the problem. What's the most likely reason for this parsing exception during a bulk index, and what's the fastest way to pinpoint the problematic field and fix it without manually sifting through thousands of lines?
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 encounter mapping conflicts or parsing errors when bulk indexing new data, causing…+
I frequently encounter mapping conflicts or parsing errors when bulk indexing new data, causing delays.
I frequently encounter mapping conflicts or parsing errors when bulk indexing new data, causing delays and forcing me to manually debug. What habit should I change to proactively prevent these issues, perhaps by always performing a schema validation or a dry run against a sample before a full bulk index, so I can catch problems before they hit production?
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.