Hi all, we run a jdbc river once per night for a complete recreation of our index.
The river - once it has been created - will run again after a restart of elasticsearch cluster (single node cluster). But what we try to achieve is a one shot river, which isn't being re-run after restart of cluster. Naturally we can trigger an event (e.g. as a cronjob) which - after the estimated end of river run - deletes the river again. But this results in additional efforts. The easiest strategy may be do delete the river right away after creating it. But I suppose in this case the running river would be stopped...? *My question is: what is the best way to create a one shot river which is not being re-run after restart of cluster?* I noticed the oneshot strategy but didn't find any documentation in https://github.com/jprante/elasticsearch-river-jdbc/wiki/Strategies. Any help would be appreciated. Regards, Abid -- 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/d642e1ff-64a1-4ac9-b2b3-bba38b5c07e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
