Elasticsearch Ingest

ElasticOfficialCreated by elastic

Skill
Workflow
Data and AI
Apache-2.0
No issues found

From the author

Load CSV, JSON, and NDJSON files into Elasticsearch indices using the bulk API and explicit mappings when field types matter. Use when batch-importing local files, converting CSV rows or JSON arrays to NDJSON bulk format, confirming cluster connectivity with elastic es info before ingest, or verifying document counts and mappings after ingest — not for Logstash pipelines, Beats, custom scripts, or index-to-index reindex.

— the description by elastic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured process for importing local data files into Elasticsearch. It focuses on converting source formats like CSV or JSON arrays into the required NDJSON bulk format, ensuring correct field typing through explicit mappings, and verifying the final ingestion status. It is designed for batch-importing tasks while maintaining data integrity through proper schema definition.

What it does

Verifies cluster connectivity before starting any data operations.
Converts CSV and JSON array files into the required NDJSON bulk format.
Creates indices with explicit mappings to ensure correct data types for numbers, dates, and booleans.
Executes bulk indexing operations using the elastic CLI.
Validates successful ingestion by comparing document counts and checking field mappings.
Provides a safe procedure for handling existing indices, including confirmation before deletion.

When to use it

When you need to perform a one-time or batch import of local data files into Elasticsearch.
When you need to ensure that CSV columns are indexed with specific types like dates or integers rather than default strings.
When you have a JSON array that needs to be indexed as individual documents.
When you need to verify that your data was indexed correctly with the expected document count and schema.

Advantages

Prevents common issues like all-text indexing by enforcing explicit mappings.
Ensures data integrity by validating document counts post-ingest.
Standardizes the conversion process from various file formats to bulk-ready NDJSON.
Promotes safe operations by requiring explicit user confirmation before destructive actions like index deletion.

Usage examples

“Import my users.csv file into a new index named users_data.”: The agent will check connectivity, inspect the CSV header, create an index with appropriate mappings for the columns, convert the CSV to NDJSON, perform the bulk load, and report the final document count.
“I have a JSON array in events.json that I need to index into the events index.”: The agent will parse the JSON array, generate the necessary action lines for each element, perform the bulk upload, and verify that the count matches the number of elements in the array.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/elastic/elasticsearch-ingest/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip elasticsearch-ingest.zip -d .agents/skills

Documentation by elastic

Elasticsearch File Ingest

Load local data files into Elasticsearch by converting them to bulk NDJSON, creating an index with the right mappings when types matter, bulk-indexing documents, and verifying the outcome.

Environment Configuration

This skill executes Elasticsearch operations through the elastic CLI. If the elastic CLI is not installed, tell the user what it is needed for. Do not guess credentials, call the HTTP API directly, or attempt other workarounds.

This skill references operations in HTTP-shorthand form (e.g., GET /, GET /_cat/indices, GET /{index}/_mapping, GET /{index}/_settings/index.mode, POST /_query). The Operations table at the end of this document maps each shorthand to the equivalent elastic CLI command — always use the CLI rather than calling the HTTP API directly.

Scope

This skill covers file → index loading through POST /_bulk. It does not use Logstash, Filebeat, Elastic Agent, Node.js ingest tools, or other sidecar pipelines. For copying documents between existing indices, use index-to-index reindex instead of re-parsing source files.

Supported source shapes:

Source shape	Example	Bulk requirement
CSV with header row	`id,name,age,...` then data rows	Parse header into field names; emit one action line + one JSON object per data row
JSON array file	`[{"a":1},{"a":2}]`	Split into per-document lines — never bulk-load the raw array as a single document
NDJSON / JSON Lines	one JSON object per line	If action and document lines already alternate, pass as-is to `POST /_bulk`; otherwise prepend action lines

Parquet, Arrow, and other binary columnar formats are out of scope unless the user converts them to CSV or JSON first.

Process

Confirm connectivity. Call GET / first. Do not start with _cat/indices, file inspection, or bulk. If GET / fails, stop and resolve CLI configuration before reading files or mutating cluster state.
Inspect the source file and classify its shape. Open the file (or sample the first lines) and decide:
- CSV — first line is a comma-separated header; subsequent lines are records. Count data rows (exclude the header) — you will report this count after load.
- JSON array — file starts with [ and contains an array of objects. Count array elements — each element becomes one indexed document, not one.
- NDJSON — one JSON value per line; lines alternate action metadata and document source, or each line is a document that still needs a preceding action line.
The decision: pick the conversion path from NDJSON Bulk Format. Never send raw CSV text or a raw JSON array body to POST /_bulk.
Choose the target index name. Use the name the user supplied, or propose a lowercase name derived from the file. Index names must be lowercase, cannot contain spaces or /, and should not start with -, _, or +.
Decide whether an explicit mapping is required. Call GET /{index}/_mapping if the index may already exist.
Create an explicit mapping before bulk loading when:
- CSV columns include numbers, dates, or booleans that must be queryable as typed fields (not plain text).
- The user asks for usable column types or aggregation-friendly fields.
- A prior load indexed everything as text/keyword strings and must be corrected.
When every field can remain string-like and the user did not specify types, dynamic mapping on first bulk ingest may suffice — but prefer explicit mappings for CSV unless the user explicitly accepts all-string typing.
Read Mapping Design for Ingest for type choices. When the index exists with wrong types, do not delete it in the same turn. Ask the user to confirm before calling DELETE /{index} and recreating it. A wrong mapping is not permission to delete. If asked whether to delete "right now", the answer is no until they explicitly confirm.
Create the index when needed. When step 4 requires explicit types (or the index does not exist), call PUT /{index} with a mappings block before bulk loading. Do not rely on dynamic mapping to infer long, date, or boolean from CSV string cells — dynamic mapping often maps ambiguous strings to text with a .keyword sub-field.
Convert the file to bulk NDJSON. Write a temporary NDJSON file where each document occupies two lines:
- Line 1 — action metadata, e.g. {"index":{"_index":"<index>"}} (add "_id" only when the user requires stable IDs).
- Line 2 — document JSON with correctly typed values (numbers as JSON numbers, booleans as true/false, dates as ISO-8601 strings such as 2023-01-15).
For CSV, map the header row to JSON field names and convert cell values to the JSON types that match the mapping from step 5. For JSON arrays, iterate each array element and emit the action line + object line pair. See worked examples in NDJSON Bulk Format.
Bulk index the documents. Call POST /_bulk with the NDJSON file produced in step 6. Inspect the response: if errors is true, read per-item error objects, fix mapping or document issues, and retry failed items after remediation. Do not assume success from a zero exit code alone.
Verify the outcome. Always confirm the load — never report counts from file inspection alone.
- Call GET /{index}/_count and compare to the expected row/element count from step 2.
- When typed columns matter, call GET /{index}/_mapping and confirm fields such as age are numeric (long / integer), dates are date, and booleans are boolean — not text.
Report the verified document count and, when relevant, the confirmed field types. If count or mapping checks fail, see Troubleshooting.

Guidelines

Connectivity first. Confirm the cluster is reachable with GET / before anything else.
Bulk only. All file loads go through POST /_bulk with NDJSON action lines — not single-document PUT loops for batch files, not ingest pipelines as a substitute for client-side CSV parsing, and not posting the untouched source file.
Pre-formed bulk NDJSON is ready. When the file already alternates action lines and document lines, pass it as-is to POST /_bulk — do not add more action lines.
Do not delete without confirmation. Elasticsearch cannot change field types in place. If the target index exists with the wrong mapping, ask the user to confirm before DELETE /{index}. If asked whether to delete "right now", the answer is no until they explicitly confirm.
JSON arrays must be split. A four-element array bulk-loaded as one document yields count 1; the correct load yields count 4.
CSV header is schema. The first CSV row names fields; each remaining row is one document. A file with one header plus five data rows must report count 5 after ingest.
Type coercion happens in the document JSON. CSV cells arrive as strings; when mappings declare long, date, or boolean, emit JSON numbers, ISO date strings, and boolean literals in the bulk body — do not rely on Elasticsearch to infer types from quoted CSV strings after dynamic mapping chose text.
Prefer explicit mappings for typed CSV. Creating the index with PUT /{index} first prevents silent all-text indexing that breaks range queries and aggregations.
Idempotent re-loads. When reloading into an existing index, ask the user before deleting data. Duplicate bulk index actions append new documents unless _id is specified.

Examples

Confirm connectivity first

GET /

Run this before reading files or calling POST /_bulk.

CSV with typed columns

Source (users.csv — header + 5 data rows):

id,name,age,signup_date,active
1,Ada Lovelace,36,2023-01-15,true

Create the index with explicit types, convert rows to NDJSON (five action+document pairs for five data rows), bulk load, then verify count 5 and mapping types. Full walkthrough: Mapping Design for Ingest and NDJSON Bulk Format.

JSON array file

Source (events.json):

[
  { "event_id": "e-1", "type": "login", "user_id": 1, "value": 12.5 },
  { "event_id": "e-2", "type": "logout", "user_id": 1, "value": 0.0 }
]

Convert to four bulk line pairs for four array elements (not one pair for the whole array). Verify GET /{index}/_count returns 4. See NDJSON Bulk Format.

NDJSON already prepared

When the file already alternates action lines and document lines, it is ready as-is. Pass it directly to POST /_bulk without adding more action lines, after confirming the target index and mappings.

When Not to Use

Continuous or streaming ingestion — use Elastic Agent or Beats to tail logs and metrics.
Complex enrichment pipelines — design server-side ingest pipelines separately; this skill still converts files to bulk NDJSON client-side before load.
Index-to-index copy or mapping migration — reindex between indices instead of exporting to files.
Very large binary columnar files — convert to CSV or JSON offline first, then follow this skill.

References

NDJSON Bulk Format — CSV and JSON-array conversion, action-line syntax, batch sizing
Mapping Design for Ingest — explicit mappings for CSV types, eval-style schemas
Troubleshooting — wrong counts, text-typed numerics, bulk item errors

Operations

HTTP API (shorthand)	`elastic` CLI command
`GET /`	`elastic es info`
`PUT /{index}`	`elastic es indices create --index '<index>' --mappings '<json>'`
`DELETE /{index}`	`elastic es indices delete --index '<index>'`
`POST /_bulk`	`elastic es bulk --index '<index>' --input-file '<ndjson-path>'`
`GET /{index}/_count`	`elastic es count --index '<index>'`
`GET /{index}/_mapping`	`elastic es indices get-mapping --index '<index>'`

Files

ATTRIBUTION.mdAdded by AutoGineer983 B
LICENSELicence file added by AutoGineer11.1 KiB
SKILL.md11.7 KiB
references/mapping-design.md4.1 KiB
references/ndjson-bulk-format.md3.7 KiB
references/troubleshooting.md2.9 KiB

LICENSE

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright 2026 Elasticsearch BV

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

The author says: Elasticsearch 8.x or 9.x, self-managed, Elastic Cloud Hosted, or Elastic Cloud Serverless; uses the bulk API available on all deployment types. Requires the `elastic` CLI ≥ 0.2 with `stack es` support.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

elastic

Publisher

Elastic (Official)

Source

elastic/agent-skills · skills/elasticsearch/elasticsearch-ingest · commit 09d879d

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

Also distributed in

elastic/agent-skills

AutoGineer is not affiliated with or endorsed by elastic or Elastic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download elasticsearch-ingest.zip