📥
Documents & CRUD

Indexing Documents

Auto vs Explicit IDs
💡 Document, indexing, EK, "LIBRARY, mein, KITAAB, RAKHNE", jaisa, hai — YA, TO, LIBRARIAN, (Elasticsearch) KHUD, EK, CATALOG, number, DE, deta hai, YA, TUM, APNA, OWN, number, DE, sakte, ho.

Documents, "_doc" endpoint, PAR, POST, karne, se, Elasticsearch, AUTOMATICALLY, EK, UNIQUE, ID, GENERATE, kar, deta hai — agar, TUM, APNA, OWN, ID, SPECIFY, karna, CHAHO, TO, "_doc/<id>" PAR, PUT, kiya, ja, sakta hai.

PUT, IDEMPOTENT, hai, — SAME, ID, ke, saath, DOBARA, PUT, karne, se, EXISTING, document, OVERWRITE, ho, jaata hai. POST, (bina, ID, ke) HAR, BAAR, EK, NAYA, document, banata hai.

POST /products/_doc
{"name": "Laptop"}

PUT /products/_doc/101
{"name": "Laptop"}
📥
Document, indexing, EK, "LIBRARY, mein, KITAAB, RAKHNE", jaisa, hai — YA, TO, LIBRARIAN, (Elasticsearch) KHUD, EK, CATALOG, number, DE, deta hai, YA, TUM, APNA, OWN, number, DE, sakte, ho.
1 / 2
⚡ Quick Recap
  • POST /_doc = auto-generated ID
  • PUT /_doc/<id> = explicit ID, idempotent (overwrite hota hai)
  • Explicit IDs source system ke existing unique IDs use karne ke liye useful hain
Is page mein (2 subtopics)

Documents, "_doc" endpoint, PAR, POST, karne, se, Elasticsearch, AUTOMATICALLY, EK, UNIQUE, ID, GENERATE, kar, deta hai — agar, TUM, APNA, OWN, ID, SPECIFY, karna, CHAHO, TO, "_doc/<id>" PAR, PUT, kiya, ja, sakta hai.

# Auto-generated ID
POST /products/_doc
{"name": "Laptop"}

# Explicit ID
PUT /products/_doc/101
{"name": "Laptop"}

PUT, IDEMPOTENT, hai, — SAME, ID, ke, saath, DOBARA, PUT, karne, se, EXISTING, document, OVERWRITE, ho, jaata hai. POST, (bina, ID, ke) HAR, BAAR, EK, NAYA, document, banata hai, NAYE, AUTO-GENERATED, ID, ke, saath.

💡Tip: Explicit, IDs, use, karna, USEFUL, hai, JAB, TUMHARE, SOURCE, system, (jaise, EK, DATABASE) mein, PEHLE, se, hi, UNIQUE, IDs, EXIST, karte, HAIN — YE, DUPLICATE, documents, avoid, karta hai.