Range query in Elasticsearch - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of a basic range query

What is the expected output count of documents matching this Elasticsearch range query on a field age with values from 20 to 30 inclusive?

Elasticsearch

{
  "query": {
    "range": {
      "age": {
        "gte": 20,
        "lte": 30
      }
    }
  }
}

A Documents with age between 20 and 30 inclusive

B Documents with age strictly greater than 20 and less than 30

C Documents with age less than or equal to 30 only

D Documents with age greater than or equal to 20 only

💡 Hint

Remember that gte means 'greater than or equal' and lte means 'less than or equal'.

The range query with gte: 20 and lte: 30 selects documents where the age field is between 20 and 30, including both 20 and 30.

❓ Predict Output

intermediate

Range query with date format

What documents will match this Elasticsearch range query on a date field?

Elasticsearch

{
  "query": {
    "range": {
      "date": {
        "gte": "2023-01-01",
        "lt": "2023-02-01",
        "format": "yyyy-MM-dd"
      }
    }
  }
}

A Documents with date from January 1, 2023 inclusive to February 1, 2023 exclusive

B evisulcxe 3202 ,1 yraurbeF ot evisulcni 3202 ,1 yraunaJ morf etad htiw stnemucoD

C Documents with date from January 1, 2023 inclusive to January 31, 2023 inclusive, but excluding February 1, 2023

D Documents with date from January 1, 2023 inclusive to January 31, 2023 inclusive

💡 Hint

lt means less than, so the upper bound excludes the date specified.

The query selects documents with date greater than or equal to 2023-01-01 and less than 2023-02-01, so it includes all dates in January 2023 but excludes February 1.

🔧 Debug

advanced

Identify the error in this range query

What error will this Elasticsearch range query produce?

Elasticsearch

{
  "query": {
    "range": {
      "price": {
        "gte": 100,
        "lte": 200
      }
    }
  }
}

A Runtime error because price field does not exist

B SyntaxError due to missing comma between gte and lte

C No error, query runs successfully

D TypeError because gte and lte values are not strings

💡 Hint

Check the JSON syntax carefully between the keys.

The JSON is invalid because there is no comma between the gte and lte keys, causing a syntax error.

🧠 Conceptual

advanced

Effect of using only lt in a range query

What documents will match this Elasticsearch range query on a field score?

Elasticsearch

{
  "query": {
    "range": {
      "score": {
        "lt": 50
      }
    }
  }
}

A Documents with score less than or equal to 50

B Documents with score greater than or equal to 50

C Documents with score less than 50

D Documents with score equal to 50 only

💡 Hint

lt means strictly less than the value.

The query matches documents where the score field is strictly less than 50, excluding 50 itself.

🚀 Application

expert

Construct a range query for exclusive bounds

Which Elasticsearch range query matches documents with temperature strictly greater than 10 and strictly less than 20?

A { "query": { "range": { "temperature": { "gte": 11, "lte": 19 } } } }

B { "query": { "range": { "temperature": { "gte": 10, "lte": 20 } } } }

C { "query": { "range": { "temperature": { "gt": 10, "lte": 20 } } } }

D { "query": { "range": { "temperature": { "gt": 10, "lt": 20 } } } }

💡 Hint

Use gt and lt for exclusive bounds.

Using gt: 10 and lt: 20 matches values strictly greater than 10 and strictly less than 20, excluding 10 and 20.