# Creating an ElasticSearch index mixing two CouchDB rivers **URL:** \ **Category:** Elasticsearch\ **Created:** [January 26, 2012, 9:24am UTC](https://discuss.elastic.co/t/creating-an-elasticsearch-index-mixing-two-couchdb-rivers/6509 "2012-01-26T09:24:43Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Daniel\_Gonzalez](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@Daniel\_Gonzalez](https://discuss.elastic.co/u/Daniel_Gonzalez)\ **Post date:** [January 26, 2012, 9:24am UTC](https://discuss.elastic.co/t/creating-an-elasticsearch-index-mixing-two-couchdb-rivers/6509/1 "2012-01-26T09:24:43Z")
I am trying to index two different CouchDB databases with Elastic Search, using a single index, but it seems that only one of the two databases is actually indexed. The documents from the other database are simply not included in the index. Is there any limitation about the number of rivers which can be connected to a given index? I am unable to find any documentation about this specific use case ... ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [January 26, 2012, 10:00am UTC](https://discuss.elastic.co/t/creating-an-elasticsearch-index-mixing-two-couchdb-rivers/6509/2 "2012-01-26T10:00:26Z")
There shouldn't be, you can have two different rivers pointing to the same index. Maybe set river.couchdb to TRACE in the logging.yml and see what gets indexed? On Thursday, January 26, 2012 at 11:24 AM, Daniel Gonzalez wrote: > I am trying to index two different CouchDB databases with Elastic > Search, using a single index, but it seems that only one of the two > databases is actually indexed. The documents from the other database > are simply not included in the index. > > Is there any limitation about the number of rivers which can be > connected to a given index? > > I am unable to find any documentation about this specific use case ... ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 26, 2012, 8:36pm UTC](https://discuss.elastic.co/t/creating-an-elasticsearch-index-mixing-two-couchdb-rivers/6509/3 "2012-01-26T20:36:58Z")
I created a gist here that should work fine for your needs : [https://gist.github.com/1684939](https://gist.github.com/1684939) [https://gist.github.com/1684939](https://gist.github.com/1684939) HTH David. De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)] De la part de Shay Banon Envoyé : jeudi 26 janvier 2012 11:00 À : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) Objet : Re: Creating an ElasticSearch index mixing two CouchDB rivers There shouldn't be, you can have two different rivers pointing to the same index. Maybe set river.couchdb to TRACE in the logging.yml and see what gets indexed? On Thursday, January 26, 2012 at 11:24 AM, Daniel Gonzalez wrote: I am trying to index two different CouchDB databases with Elastic Search, using a single index, but it seems that only one of the two databases is actually indexed. The documents from the other database are simply not included in the index. Is there any limitation about the number of rivers which can be connected to a given index? I am unable to find any documentation about this specific use case ... ---
**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, 3:41am UTC](https://discuss.elastic.co/t/creating-an-elasticsearch-index-mixing-two-couchdb-rivers/6509/4 "2017-07-06T03:41:19Z")