# How to handle duplicate records in datastreams using fingerprint

**URL:** https://discuss.elastic.co/t/how-to-handle-duplicate-records-in-datastreams-using-fingerprint/384260
**Category:** Logstash
**Created:** [December 26, 2025, 9:49am UTC](https://discuss.elastic.co/t/how-to-handle-duplicate-records-in-datastreams-using-fingerprint/384260 "2025-12-26T09:49:45Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [December 26, 2025, 11:34am UTC](https://discuss.elastic.co/t/how-to-handle-duplicate-records-in-datastreams-using-fingerprint/384260/3 "2025-12-26T11:34:00Z")

</div>

As Tortoise said, data streams are append-only - approx. write once, read many times indices.

Check [a similar topic](https://discuss.elastic.co/t/prevent-duplicates-in-a-data-stream/283076), [the blog](https://www.elastic.co/blog/efficient-duplicate-prevention-for-event-based-data-in-elasticsearch) and [GHub](https://github.com/elastic/elasticsearch/issues/44794).

---

_[View the full topic](https://discuss.elastic.co/t/how-to-handle-duplicate-records-in-datastreams-using-fingerprint/384260)._