# Elasticsearch Data Streams: Update Strategies, Concerns, and Alternatives **URL:** \ **Category:** Elasticsearch\ **Tags:** datastreams\ **Created:** [January 8, 2024, 7:12am UTC](https://discuss.elastic.co/t/elasticsearch-data-streams-update-strategies-concerns-and-alternatives/350546 "2024-01-08T07:12:56Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![jainesh\_singh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jainesh_singh/32/119545_2.png) [@jainesh\_singh](https://discuss.elastic.co/u/jainesh_singh)\ **Post date:** [January 10, 2024, 5:45am UTC](https://discuss.elastic.co/t/elasticsearch-data-streams-update-strategies-concerns-and-alternatives/350546/5 "2024-01-10T05:45:01Z")
Hey Christian, Thanks for your help. I feel the solution you suggested would work for me. Using your suggested approach, I am facing certain challenges in Logstash implementation. Could you share some light on : > [@Updating Elasticsearch Indices conditionally when referring to 2 database table](https://discuss.elastic.co/t/updating-elasticsearch-indices-conditionally-when-referring-to-2-database-table/350663): > > Description: We have two SQL tables: FileDetail for storing file details and FileUserActivity for file activities. Using Logstash, we're indexing data into Elasticsearch with a flat index approach, combining file details and activities in a single document. However, when file details change in the FileDetail table (e.g., file owner modification), we need a solution to update all previous Elasticsearch indices related to that file. Database Tables: FileDetail Table: Columns: fileid, ..., o… --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-data-streams-update-strategies-concerns-and-alternatives/350546)._