Combining rivers into one document

For a project I'm currently working on I have two rivers, one JDBC and a
CouchDB river, each going to the same index, but a different type. The
documents comming from this rivers are related to each other: The JDBC
river gives basic product information and the CouchDB gives extended
product information.

Now I want to search for documents based on two fields, one on each type.
As Elasticsearch doesn't support joining documents (at least not for as far
as I can see), I was searching for a way of combining the to rivers into 1
document, but it looks like the documents get overwritten instead of
extended with the new properties.

Is this kind of behavior possible or should I approach this in a different
way?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Definitely you should manage that in an other tool or layer.
For example in a service layer or using an ETL.

Rivers are not designed to aggregate documents from different sources. It's just a helper to start very quickly with elasticsearch but at the end of the day, most of the users prefers to manage that injection process from outside elasticsearch nodes themselves.

My 2 cents

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

5 novembre 2013 at 09:24:24, Peter Beernink (beerninkp@gmail.com) a écrit:

For a project I'm currently working on I have two rivers, one JDBC and a CouchDB river, each going to the same index, but a different type. The documents comming from this rivers are related to each other: The JDBC river gives basic product information and the CouchDB gives extended product information.

Now I want to search for documents based on two fields, one on each type. As Elasticsearch doesn't support joining documents (at least not for as far as I can see), I was searching for a way of combining the to rivers into 1 document, but it looks like the documents get overwritten instead of extended with the new properties.

Is this kind of behavior possible or should I approach this in a different way?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

+1 for David

Please note that JDBC river is not a product and can not provide product
information.

It is just a helper to quickly load some data into ES, for example, to
convince the boss for a POC within a few hours or days. There is no
intention to replace ETL products.

Jörg

--
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.
For more options, visit https://groups.google.com/groups/opt_out.