◆ Elasticsearch

Create or update mapping

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 new mapping for the 'logs-2024-07-26' index. I need 'event_id' to be a keyword field…+
Create a new mapping for the 'logs-2024-07-26' index. I need 'event_id' to be a keyword field and 'timestamp' to be a date field in strict_date_optional_time format. All other fields should use dynamic mapping.
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 push this new log data into production, set up the mapping for the 'customer_events'…+
Before I push this new log data into production, set up the mapping for the 'customer_events' index so that I can easily filter and sort by 'user_id' and 'event_type' without performance hits, and ensure 'request_time' is correctly parsed for time-based queries. Flag any potential issues with how existing data might be handled.
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 'metrics-prod' index is failing to ingest new documents, throwing mapping conflict errors,…+
The new 'metrics-prod' index is rejecting data because of mapping conflicts, but I can't see what's wrong.
The 'metrics-prod' index is failing to ingest new documents, throwing mapping conflict errors, but the current mapping looks fine on the surface. I'm afraid of pushing a change that breaks existing dashboards. The ops team is leaning on me for a fix before end of day. What's the most likely underlying conflict, and what's the safest way to diagnose and resolve it without downtime?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly getting pulled into mapping conflicts when new data streams go live, often…+
I keep having to manually fix mapping issues after new data sources are introduced.
I'm constantly getting pulled into mapping conflicts when new data streams go live, often because a field type was assumed or not explicitly defined. It's eating up my time and causing delays for the analytics team. What habit should I change in my early design process to proactively define and validate mappings before data ever hits the 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.