Boolean and binary types in Elasticsearch - Step-by-Step Execution

Concept Flow - Boolean and binary types

Start

↓

Define Field Type

↓

Boolean Type

↓

Accepts true/false

↓

Stores as true/false

↓

Binary Type

↓

Accepts base64 strings

↓

Stores as binary data

↓

Use in documents

↓

Query & Retrieve

↓

End

This flow shows how Elasticsearch handles Boolean and Binary types: defining fields, accepting values, storing them, and using them in documents.

Execution Sample

Elasticsearch

PUT /my_index
{
  "mappings": {
    "properties": {
      "is_active": {"type": "boolean"},
      "file_data": {"type": "binary"}
    }
  }
}

Defines an index with a boolean field 'is_active' and a binary field 'file_data'.

Execution Table

Step	Action	Field	Input Value	Stored Value	Notes
1	Define boolean field	is_active	N/A	N/A	Field type set to boolean
2	Define binary field	file_data	N/A	N/A	Field type set to binary
3	Index document	is_active	true	true	Boolean true stored as true
4	Index document	file_data	"SGVsbG8="	<binary data>	Base64 string decoded and stored
5	Retrieve document	is_active	N/A	true	Boolean value retrieved as true
6	Retrieve document	file_data	N/A	"SGVsbG8="	Binary data returned as base64 string
7	Exit	N/A	N/A	N/A	All fields processed successfully

💡 All fields defined and data indexed and retrieved successfully.

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	After Step 6	Final
is_active	undefined	true	true	true	true	true
file_data	undefined	undefined	<binary data>	<binary data>	"SGVsbG8="	"SGVsbG8="

Key Moments - 2 Insights

Why does the binary field store base64 strings but return base64 strings on retrieval?

Because Elasticsearch expects binary data to be sent as base64 strings, it decodes and stores the raw binary internally, but when retrieving, it encodes the binary back to base64 for safe transport. See execution_table rows 4 and 6.

Can the boolean field accept strings like "true" or only boolean true/false?

Elasticsearch accepts boolean values true or false directly. Strings like "true" are converted internally if possible, but best practice is to send actual boolean values. See execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the input value for the binary field?

A "SGVsbG8="

B true

C <binary data>

D false

💡 Hint

Check the 'Input Value' column at step 4 in the execution_table.

At which step is the boolean value retrieved from the index?

A Step 3

B Step 6

C Step 5

D Step 2

💡 Hint

Look for 'Retrieve document' action for 'is_active' field in execution_table.

If you send the string "false" instead of boolean false to the boolean field, what likely happens?

A It stores as string "false"

B It stores as boolean false

C It causes an error

D It stores as boolean true

💡 Hint

Refer to key_moments about boolean field input handling.

Concept Snapshot

Boolean and binary types in Elasticsearch:
- Boolean fields store true/false values.
- Binary fields store base64-encoded binary data.
- Binary input must be base64 strings; stored as raw binary.
- Retrieval of binary fields returns base64 strings.
- Boolean fields accept true/false values directly.

Full Transcript

This visual execution trace shows how Elasticsearch handles Boolean and Binary types. First, fields are defined with their types. Boolean fields accept true or false values and store them as such. Binary fields accept base64 encoded strings, decode them to store raw binary data, and return base64 strings when retrieved. The execution table traces defining fields, indexing documents with these fields, and retrieving them. Variable tracking shows how values change through steps. Key moments clarify common confusions about input formats and storage. The quiz tests understanding of input values, retrieval steps, and type handling. The snapshot summarizes key points about these types in Elasticsearch.