# Upsert and Dedup

Upsert and dedup are for tables that ingest repeated keys. Use them when the current value matters more than the raw event history, or when duplicate events should not fan out into duplicate query results.

## Choose the right behavior

Use upsert when newer rows should replace older rows for the same primary key.

Use dedup when repeated records should be filtered out and only the first or unique representation should remain.

## Operational notes

These patterns need a careful schema, a stable primary key, and ingestion flow that understands the table-level metadata Pinot uses to keep the result consistent.

The strongest detail still lives in the original docs under [Upsert and Dedup](https://docs.pinot.apache.org/build-with-pinot/ingestion/upsert-dedup).

## What this page covered

This page covered the difference between upsert and dedup and when each is the better fit.

## Next step

Read [Formats and Filesystems](https://docs.pinot.apache.org/build-with-pinot/ingestion/formats-filesystems) to decide how Pinot should read source data and store generated segments.

## Related pages

* [Ingestion](https://docs.pinot.apache.org/build-with-pinot/ingestion)
* [Batch Ingestion](https://docs.pinot.apache.org/build-with-pinot/ingestion/batch-ingestion)
* [Stream Ingestion](https://docs.pinot.apache.org/build-with-pinot/ingestion/stream-ingestion)
* [Formats and Filesystems](https://docs.pinot.apache.org/build-with-pinot/ingestion/formats-filesystems)
* [Original Upsert and Dedup Docs](https://docs.pinot.apache.org/build-with-pinot/ingestion/upsert-dedup)