Concepts for Elasticsearchs
Elasticsearch concepts are the building blocks of the engine: a document is a JSON object, an index is a collection of documents, and a mapping defines each field's type. Analyzers break text into tokens at index time, which is what makes full-text search possible in Elasticsearch.
Stage: Fundamentals · Part of the Elasticsearch roadmap · Last reviewed 19 November 2026
What to learn in Concepts
- Describe how documents, indices, shards and replicas relate to one another
- Define an explicit mapping with text, keyword, date and numeric fields
- Explain how an analyzer applies a tokenizer and token filters to text
- Test an analyzer with the _analyze API and read the tokens it returns
- Decide when a string field should be text, keyword or both
Concepts interview questions
What is the difference between text and keyword field types?
A text field is analyzed into tokens, so it supports full-text search by individual words. A keyword field is stored as one exact value, which suits filtering, sorting and aggregations such as status or email. Many string fields use both through multi-fields.
What is an inverted index?
It maps each unique term to the list of documents containing it, like the index at the back of a book. Searching for a term becomes a lookup of that list rather than a scan of every document, which is why Lucene-based search is fast.
Where Concepts fits in the Elasticsearch roadmap
Concepts 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