Is it possible to create custom rivers of our own? I've a situation where a
river makes sense, but I need to touch two external datasources. I've read
through the river doco here:
Searched the mailing list for other people creating custom rivers and
couldn't find any references.
I've had a browse through the source and binary distro's. I can see that
the three current river plugins are included in the jar, but can't work out
how they are configured/included.
If I could somehow create my own river plugin, what would be the recommended
approach to including/running it inside my elastic cluster?
On Tue, Oct 12, 2010 at 4:29 AM, Owen Butler wrote:
Is it possible to create custom rivers of our own?
Yes, i guess it is possible in elasticsearch. I had gone through the
CouchDB river code and it looks pretty easy to make a new one.
I've a situation where a
river makes sense, but I need to touch two external datasources.
Can you explain a bit about "two external data-sources" ? Do you mean
for a single index, you want to index data using two rivers, each
accessing two separate data sources ?
I've had a browse through the source and binary distro's. I can see that
the three current river plugins are included in the jar, but can't work out
how they are configured/included.
An example of how to configure a CouchDB river is given here:
If I could somehow create my own river plugin, what would be the recommended
approach to including/running it inside my elastic cluster?
It would be best to use one of the existing river plugins as a
starting point and start building up your own plug-in. Personally, I
would recommend the CouchDB river plugin as a starting point
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
