Why Elasticsearch exists - Quick Recap

Recall & Review

beginner

What problem does Elasticsearch solve?

Elasticsearch helps to quickly search and analyze large amounts of data in real time, which is hard to do efficiently with traditional databases.

beginner

Why is speed important in Elasticsearch?

Because users want instant results when searching through huge data sets, Elasticsearch is designed to be very fast and scalable.

intermediate

How does Elasticsearch handle large data volumes?

It breaks data into smaller pieces called shards and distributes them across many servers, so it can search in parallel and handle more data.

intermediate

What makes Elasticsearch different from a regular database?

Unlike regular databases that focus on storing data, Elasticsearch is built for fast searching and analyzing text and complex data structures.

beginner

Why was Elasticsearch created as an open-source tool?

To allow developers everywhere to use, improve, and adapt it freely for many different search and analytics needs.

What is the main purpose of Elasticsearch?

A Fast search and analysis of large data

B Storing small amounts of data

C Creating user interfaces

D Managing network connections

Elasticsearch is designed to quickly search and analyze large volumes of data.

How does Elasticsearch improve search speed?

A By using a single server

B By breaking data into shards and searching in parallel

C By storing data in spreadsheets

D By limiting data size

Elasticsearch splits data into shards and distributes them to search in parallel, speeding up queries.

Which of these is NOT a reason why Elasticsearch exists?

A To provide real-time search

B To handle large data volumes

C To analyze complex data quickly

D To replace all traditional databases

Elasticsearch complements databases but does not aim to replace all traditional databases.

Why is Elasticsearch open source?

A To charge high fees

B To keep it secret

C To allow community contributions and free use

D To limit its use

Being open source lets developers use and improve Elasticsearch freely.

What kind of data is Elasticsearch especially good at searching?

A Text and complex structured data

B Only numbers

C Images only

D Audio files only

Elasticsearch excels at searching text and complex data structures quickly.

Explain in your own words why Elasticsearch was created and what problem it solves.

Think about how hard it is to find information quickly in huge piles of data.

Describe how Elasticsearch manages to search large amounts of data quickly.

Imagine dividing a big task into smaller parts to finish faster.

Practice

1. Why was Elasticsearch created?
Elasticsearch is mainly used because:

easy

A. It helps find and analyze large amounts of data quickly

B. It is a programming language for building websites

C. It stores data only in spreadsheets

D. It is used to design graphics and images

Solution

1. Step 1: Understand Elasticsearch's purpose

   Elasticsearch is designed to search and analyze data fast, especially large or complex data.

2. Step 2: Compare options with Elasticsearch's use

   The options claiming it is a programming language, stores data only in spreadsheets, or is used for graphics are incorrect.

3. Final Answer:

   It helps find and analyze large amounts of data quickly -> Option A

4. Quick Check:

   Elasticsearch = Fast data search and analysis [OK]

Hint: Elasticsearch = fast search and analysis tool [OK]

Common Mistakes:

• Thinking Elasticsearch is a programming language
• Confusing it with spreadsheet software
• Assuming it is for graphic design

2. Which of the following is the correct way to send a search query to Elasticsearch?

easy

A. Writing SQL queries directly in Elasticsearch console

B. Using JSON format over HTTP

C. Using XML files uploaded manually

D. Sending plain text emails to Elasticsearch server

Solution

1. Step 1: Identify Elasticsearch query method

   Elasticsearch uses JSON queries sent over HTTP to interact with data.

2. Step 2: Eliminate incorrect methods

   SQL, XML uploads, and emails are not how Elasticsearch receives queries.

3. Final Answer:

   Using JSON format over HTTP -> Option B

4. Quick Check:

   Elasticsearch queries = JSON + HTTP [OK]

Hint: Elasticsearch queries use JSON over HTTP [OK]

Common Mistakes:

• Assuming Elasticsearch uses SQL queries
• Thinking XML files are used for queries
• Believing email can send queries

3. What will Elasticsearch do when you send this JSON query?

{"query": {"match": {"title": "coffee"}}}

medium

A. Return an error because the query is invalid

B. Delete all documents with the title 'coffee'

C. Update the title field to 'coffee' in all documents

D. Search documents where the title contains the word 'coffee'

Solution

1. Step 1: Understand the JSON query structure

   The query uses "match" on the "title" field with the word "coffee" to find matching documents.

2. Step 2: Identify the query action

   This is a search query, not a delete or update command, so it returns matching documents.

3. Final Answer:

   Search documents where the title contains the word 'coffee' -> Option D

4. Quick Check:

   Match query = search for matching text [OK]

Hint: Match query finds documents containing the word [OK]

Common Mistakes:

• Confusing search with delete or update
• Thinking the query syntax is invalid
• Assuming it changes data instead of searching

4. You wrote this query to find documents with 'apple' in the description:

{"query": {"match": {"description": "apple"}}

But Elasticsearch returns an error. What is wrong?

medium

A. The field name 'description' is invalid

B. The word 'apple' is not allowed in queries

C. The JSON query is missing a closing brace '}'

D. Elasticsearch does not support match queries

Solution

1. Step 1: Check JSON syntax carefully

   The query is missing a closing brace '}' at the end, making it invalid JSON.

2. Step 2: Verify other options

   Words like 'apple' are allowed, 'description' can be a valid field, and match queries are supported.

3. Final Answer:

   The JSON query is missing a closing brace '}' -> Option C

4. Quick Check:

   JSON syntax error = missing brace [OK]

Hint: Always check JSON braces and commas carefully [OK]

Common Mistakes:

• Ignoring JSON syntax errors
• Assuming certain words are banned
• Thinking field names must be predefined

5. You have a large dataset with millions of records and want to quickly find all entries mentioning 'travel' in any text field. Why is Elasticsearch a good choice for this?

hard

A. Because it indexes data for fast full-text search across many fields

B. Because it stores data only in small files for quick access

C. Because it uses SQL joins to combine travel data efficiently

D. Because it compresses data to save disk space only

Solution

1. Step 1: Understand Elasticsearch's indexing

   Elasticsearch creates indexes that allow very fast full-text search across large datasets and multiple fields.

2. Step 2: Evaluate other options

   It does not rely on small files only, SQL joins, or just compression for speed.

3. Final Answer:

   Because it indexes data for fast full-text search across many fields -> Option A

4. Quick Check:

   Indexing = fast search on big data [OK]

Hint: Indexing enables fast search on large data [OK]

Common Mistakes:

• Thinking Elasticsearch uses SQL joins
• Believing it only compresses data
• Assuming it stores data in small files only