Ingestion

Plan Pinot ingestion around batch, stream, upsert, dedup, formats, filesystems, and transformation choices.

Ingestion is where Pinot tables become real. Start here to choose the right path for batch or stream data, then refine the design with upsert, dedup, file format, filesystem, transform, and aggregation decisions.

The detailed controller and table-config material belongs in Reference. This section stays focused on data flow and operational choices.

Start Here

• Batch Ingestion - for data that arrives in files or lands in a warehouse-style batch flow.

• Stream Ingestion - for Kafka-style or other event streams that should be queryable quickly.

• Upsert and Dedup - for tables that need one canonical row per key instead of raw event history.

• Formats and Filesystems - for source formats, file systems, and deep-storage choices.

• Transformations and Aggregations - for ingest-time cleanup and pre-aggregation decisions.

Related Existing Docs

• Import Data

• Data Ingestion Overview

• Ingestion Transformations

• Ingestion Aggregations

• Supported Data Formats

• File Systems

What this page covered

This landing page defines the ingestion subtree and points to the main decision pages.

Next step

Read Batch Ingestion if your source data arrives in files or prebuilt segments.

Related pages

• Batch Ingestion

• Stream Ingestion

• Upsert and Dedup

• Formats and Filesystems

• Transformations and Aggregations