Creating an ElasticSearch index mixing two CouchDB rivers

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 ...

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 ...

I created a gist here that should work fine for your needs : https://gist.github.com/1684939 https://gist.github.com/1684939

HTH

David.

De : elasticsearch@googlegroups.com [mailto:elasticsearch@googlegroups.com] De la part de Shay Banon
Envoyé : jeudi 26 janvier 2012 11:00
À : 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 ...