A while ago I used a plugin on a project to control the migration to, and the maintenance of, a secondary data source/index in ElasticSearch. It worked really well and avoided lots of messy dependency management in the host application, as all the logic was "hidden" behind an ES rest end-point.
But I was never really sure how scalable this was. I have two questions: 1.) when I register a plugin, is that available for all nodes? (I'm assuming "yes", which would mean controlling parallel/overlapping call outs is important) 2.) when i call my end-point, I have a Client Object passed in the constructor: when I debug this, it is an instance of NodeClient which presumably means I am working on a single node. Is it possible to construct a TransportClient from this, so that I can address more than node and take advantage of e.g. bulk imports in parallel? Regarding 2.), I've had a look at the JDBC River Code and the Feeder mode (addressing the cluster from a component running in a separate JVM) seems to be there precisely because of this drawback. The River mode seems to work off one node like my plugin did/does. Is my understanding correct? Andrew -- 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/16664d7b-3934-4a90-8b1f-209ede3ff08c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
