Ingestion for Elasticsearchs
Elasticsearch ingestion is the process of getting data into indices. You can index single documents with the index API, load many at once with the _bulk API, and transform documents on the way in with ingest pipelines or shippers such as Beats and Logstash.
Stage: Fundamentals · Part of the Elasticsearch roadmap · Last reviewed 19 November 2026
What to learn in Ingestion
- Index a document with a chosen ID and let Elasticsearch generate one when omitted
- Load thousands of documents efficiently with the _bulk API and read its per-item errors
- Create an ingest pipeline that parses, renames or enriches fields before storage
- Update and delete documents and understand why updates reindex the whole document
- Reindex data into a new index after changing a mapping
Ingestion interview questions
Why use the bulk API instead of many single index requests?
Each single request has network and coordination overhead. The bulk API sends many operations in one request, which raises throughput considerably. You must still check the response, because individual items can fail while the overall request returns 200.
How do you change the type of an existing field?
You cannot change a field's mapping in place. Create a new index with the corrected mapping, copy the data across with the _reindex API, and switch an alias from the old index to the new one so clients see no downtime.
Where Ingestion fits in the Elasticsearch roadmap
Ingestion belongs to the Fundamentals stage (beginner level), which takes about 15 hours. Indexing and mapping.
Other units in this stage
Back to the full Elasticsearch roadmap