In my project (with postgresql), I choose to push documents in ES each time I create, update or delete an Hibernate entity.
That's why I don't use a river by now.
Problem is when I need to reindex all my documents from my database.
At the present time, I create a "batch" for that but I'm thinking of using Talend for that.
That's not a river, for sure !
Le 6 déc. 2011 à 18:51, Otis Gospodnetic email@example.com a écrit :
OK, so this is still external, except it's a push instead of a pull
(like in Solr's DIH).
So no MySQL River.
Is there a technical reason why one could not implement a MySQL
River, or is it just that nobody had this MySQL==>ES itch yet?
Sematext is Hiring World-Wide -- http://sematext.com/about/jobs.html
On Dec 6, 3:08 am, Damien Hardy damienhardy....@gmail.com wrote:
Maybe you can look after MySQL trigger to fire a POST request to
elasticsearch base on UDF like :http://code.google.com/p/mysql-udf-http/
2011/12/5 Otis Gospodnetic otis.gospodne...@gmail.com
How do people do MySQL (or any other RDBMS) indexing in bulk an
incrementally? Is there something like Solr's DataImportHandler in
I know there are Rivers and I assume it makes sense to implement a
tool for indexing database content as a River, but I don't see a MySQL
Or are people writing standalone and external indexer apps that push
data from DB to ES? (and thus probably creating a SPOF in their
Sematext is Hiring World-Wide --http://sematext.com/about/jobs.html