Why Partial updates in Elasticsearch? - Purpose & Use Cases

The Big Idea

What if you could fix just one tiny detail without rewriting the whole story?

The Scenario

Imagine you have a huge document stored in Elasticsearch, like a detailed user profile with many fields. Now, you want to change just the user's phone number. Without partial updates, you'd have to fetch the entire document, change the phone number manually, and then send the whole document back to Elasticsearch.

The Problem

This manual way is slow because you transfer and rewrite the entire document even if only one small part changes. It's also risky because you might accidentally overwrite other fields or lose data if you miss something. Plus, it wastes bandwidth and processing power.

The Solution

Partial updates let you send only the changes you want to make. Elasticsearch applies these changes directly to the stored document without needing the full data. This makes updates faster, safer, and more efficient.

Before vs After

✗ Before

GET /index/_doc/1
// fetch full document
PUT /index/_doc/1
{ "name": "Alice", "phone": "12345", "email": "[e-mail]" }

✓ After

POST /index/_update/1
{ "doc": { "phone": "12345" } }

What It Enables

Partial updates enable quick, precise changes to documents without the overhead of resending or risking full document replacement.

Real Life Example

In a social media app, when a user changes their profile picture, partial updates let you update just the picture URL without touching the rest of their profile data.

Key Takeaways

Manual full-document updates are slow and risky.

Partial updates send only the changed fields.

This makes updates faster, safer, and more efficient.