My thoughts on this. If you can modify the application which writes to your RDBMS, then you should do it from there. If not, it depends on your data I'd say.
For example, if your application delete data instead of marking them as deleted, you will basically have to reindex everything often. If your database contains timestamp for your data, then you can use that to only index/remove changes. If your entities are not flat, it means that you have to run multiple SQL calls to generate a full JSON object. In that case, you should write your own code as a batch or so. > Le 15 oct. 2014 à 09:16, Jorge von Rudno <[email protected]> a > écrit : > > Dear College, > > I have used "river" in order to load an index in elasticsearch from > postgresql and now I want to keep the index synchronized with the database. > Can I use river for this purpose?, how? or there are another tool to do this? > > At the beginning I have considered to write a trigger and a stored procedure, > but If "river" is designed to do this I will prefer use it. > > kind regards. > > Jorge von Rudno > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAFqKu%3DaF86B2nqc9aXyUA77OXjZOXQihfT1x0QbuLpNWXe8HnQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7F4E864F-11C4-41E1-86D4-BEA6F8D1AC36%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
