# Best approach to keep DataStore and Index in sync? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 29, 2013, 2:58am UTC](https://discuss.elastic.co/t/best-approach-to-keep-datastore-and-index-in-sync/11371 "2013-03-29T02:58:44Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Amarthya\_Master](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@Amarthya\_Master](https://discuss.elastic.co/u/Amarthya_Master)\ **Post date:** [March 29, 2013, 2:58am UTC](https://discuss.elastic.co/t/best-approach-to-keep-datastore-and-index-in-sync/11371/1 "2013-03-29T02:58:44Z")
You can have a push model or a pull mdoel for updating indexes incrementally to keep the datastore and the index in sync. Bypull, using the river, say JDBC if it is a sql DB or writing your own river. By push, implenenting an idexer that updates the index using the API calls. What is the best approach, if you have a complex schema for your index, say inner object that are complex types themselves. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:43am UTC](https://discuss.elastic.co/t/best-approach-to-keep-datastore-and-index-in-sync/11371/2 "2017-07-06T02:43:45Z")