# Data Ingestion From Cloud Firestore Into Elasticsearch

**URL:** <https://discuss.elastic.co/t/data-ingestion-from-cloud-firestore-into-elasticsearch/175865>\
**Category:** Elasticsearch\
**Created:** [April 8, 2019, 3:02pm UTC](https://discuss.elastic.co/t/data-ingestion-from-cloud-firestore-into-elasticsearch/175865 "2019-04-08T15:02:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Muhammad\_Ezzat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammad_ezzat/32/43654_2.png) [@Muhammad\_Ezzat](https://discuss.elastic.co/u/Muhammad_Ezzat)\
**Post date:** [April 8, 2019, 3:02pm UTC](https://discuss.elastic.co/t/data-ingestion-from-cloud-firestore-into-elasticsearch/175865/1 "2019-04-08T15:02:08Z")

</div>

We are trying to ingest data from [Cloud Firestore](https://firebase.google.com/docs/firestore/) into Elasticsearch.  
We found this plugin - [elasticstore](https://github.com/acupajoe/elasticstore) - created by the community; it is very helpful, but it has a serious drawback. The following is a quotation from the plugin documentation:  
"Upon starting (and restarting) ALL data is re-indexed unless you choose to filter it yourself. This is a VERY expensive operation, as you will have to perform reads on every document you have in your `collection` ."  
Obviously, that affects directly the cost on firestore as the pricing is based on the number of document reads.  
It would be very helpful if anyone can provide us with guidance in this usecase or refer to any other tools, plugins or any workaround that can come in handy.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 6, 2019, 3:02pm UTC](https://discuss.elastic.co/t/data-ingestion-from-cloud-firestore-into-elasticsearch/175865/2 "2019-05-06T15:02:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
