Numeric field types in Elasticsearch

Introduction

Numeric field types let you store numbers in Elasticsearch so you can search, sort, and calculate with them easily.

When you want to store ages, prices, or quantities in your data.

When you need to filter results by number ranges, like products costing between $10 and $50.

When you want to sort search results by numeric values, like highest rating first.

When you want to do math operations on your data, like averages or sums.

When you want to store dates as timestamps (numbers) for fast searching.

Syntax

Elasticsearch

PUT /my_index
{
  "mappings": {
    "properties": {
      "field_name": {
        "type": "integer" | "long" | "float" | "double" | "short" | "byte" | "half_float" | "scaled_float"
      }
    }
  }
}

Choose the numeric type based on the size and precision you need.

Scaled_float lets you store decimals as integers with a scaling factor for accuracy.

Examples

This example creates a products index with price as a decimal number and stock as a whole number.

Elasticsearch

PUT /products
{
  "mappings": {
    "properties": {
      "price": { "type": "float" },
      "stock": { "type": "integer" }
    }
  }
}

Here, age is a small integer and score is a decimal stored as an integer multiplied by 100.

Elasticsearch

PUT /users
{
  "mappings": {
    "properties": {
      "age": { "type": "short" },
      "score": { "type": "scaled_float", "scaling_factor": 100 }
    }
  }
}

Sample Program

This creates a library index with pages as an integer and rating as a float. Then it adds a book and searches for books with at least 300 pages.

Elasticsearch

PUT /library
{
  "mappings": {
    "properties": {
      "pages": { "type": "integer" },
      "rating": { "type": "float" }
    }
  }
}

POST /library/_doc
{
  "pages": 350,
  "rating": 4.5
}

GET /library/_search
{
  "query": {
    "range": {
      "pages": {
        "gte": 300
      }
    }
  }
}

Important Notes

Always pick the smallest numeric type that fits your data to save space.

Elasticsearch stores numbers in a way that makes searching and sorting very fast.

Remember to define your mappings before adding data to avoid errors.

Summary

Numeric field types store numbers for searching, sorting, and calculations.

Choose types like integer, float, or scaled_float based on your data needs.

Define numeric fields in mappings before adding documents.

Practice

1.

Which numeric field type in Elasticsearch should you use to store whole numbers without decimals?

easy

A. double

B. integer

C. float

D. text

Solution

1. Step 1: Understand numeric field types

   Integer type stores whole numbers without decimals, suitable for counts or IDs.

2. Step 2: Compare with other types

   Float and double store decimal numbers; text is for strings, not numbers.

3. Final Answer:

   integer -> Option B

4. Quick Check:

   Whole numbers = integer [OK]

Hint: Whole numbers use integer type, decimals need float/double [OK]

Common Mistakes:

• Choosing float or double for whole numbers
• Using text type for numbers
• Confusing integer with long for small numbers

2.

Which of the following is the correct way to define a long numeric field in an Elasticsearch mapping?

{
  "mappings": {
    "properties": {
      "user_id": {
        "type": "_____"
      }
    }
  }
}

easy

A. "long"

B. "integer"

C. "float"

D. "keyword"

Solution

1. Step 1: Identify the field type for large whole numbers

   Long type stores larger whole numbers than integer, suitable for big IDs.

2. Step 2: Match the correct type string in mapping

   Use "long" as the type value in the mapping JSON for such fields.

3. Final Answer:

   "long" -> Option A

4. Quick Check:

   Big whole numbers = "long" [OK]

Hint: Use "long" for large whole numbers in mapping [OK]

Common Mistakes:

• Using "integer" for very large numbers
• Using "keyword" which is for text
• Using "float" for whole numbers

3.

Given this Elasticsearch mapping snippet, what type of number can price store?

{
  "mappings": {
    "properties": {
      "price": {
        "type": "float"
      }
    }
  }
}

medium

A. Boolean true/false values

B. Only whole numbers

C. Text values representing numbers

D. Decimal numbers with floating point

Solution

1. Step 1: Check the type assigned to price

   The type is "float", which stores decimal numbers with floating point precision.

2. Step 2: Understand what float means

   Float allows decimals, unlike integer or long which store whole numbers only.

3. Final Answer:

   Decimal numbers with floating point -> Option D

4. Quick Check:

   Float type = decimals allowed [OK]

Hint: Float type stores decimal numbers, not just whole numbers [OK]

Common Mistakes:

• Thinking float stores only whole numbers
• Confusing float with text or boolean
• Assuming float stores exact decimal precision always

4.

What is wrong with this Elasticsearch mapping for a numeric field?

{
  "mappings": {
    "properties": {
      "score": {
        "type": "integer",
        "index": "not_analyzed"
      }
    }
  }
}

medium

A. 'type' should be 'float' instead of 'integer'

B. 'score' field name is not allowed

C. 'index' parameter is invalid for numeric fields

D. Mapping syntax is missing a closing brace

Solution

1. Step 1: Review the 'index' parameter usage

   Numeric fields do not support 'index' with 'not_analyzed'; this is for text fields.

2. Step 2: Confirm correct mapping for numeric fields

   Numeric fields are indexed by default and do not use 'not_analyzed'.

3. Final Answer:

   'index' parameter is invalid for numeric fields -> Option C

4. Quick Check:

   Numeric fields don't use 'index': 'not_analyzed' [OK]

Hint: Don't use 'index':'not_analyzed' on numeric fields [OK]

Common Mistakes:

• Using text field options on numeric fields
• Changing type unnecessarily
• Ignoring Elasticsearch mapping syntax rules

5.

You want to store product weights that can be very large and may have decimals. Which Elasticsearch numeric field type is best?

hard

A. double

B. long

C. float

D. integer

Solution

1. Step 1: Analyze the requirements for product weights

   Weights can be very large and have decimals, so the type must support large range and decimals.

2. Step 2: Compare float and double types

   Float supports decimals but has less precision and smaller range than double.

3. Step 3: Choose the best type for large decimal numbers

   Double supports large decimal numbers with higher precision, suitable for weights.

4. Final Answer:

   double -> Option A

5. Quick Check:

   Large decimals = double type [OK]

Hint: Use double for large decimal numbers needing precision [OK]

Common Mistakes:

• Choosing integer or long which don't support decimals
• Using float which may lose precision
• Ignoring size and precision needs