just checking this approach will work. If I install the RabbitMQ river ala
the ES docs with that funky bit of curl, that I can use the 2.2.0 version of
the amqp-client dependency in a project ala Maven:
and then simply publish messages containing JSON text ala the bulk API.
That's the way I read the River docs, I think this is right.... ?
In a clustered ES instance, I understand the Rivers are singletons, so will
only be on one node. From a client application sending messages, how will
it know which host to send the RabbitMQ messages to exactly.. ?
Or is the proper way to setup a RabbitMQ server on some host 'RabbitMQHost'
and have the river singleton just be the 'consumer' client of the queue ?
(so we have an ES process, as well as separate RabbitMQ process perhaps
sharing the same hardware, perhaps not).
I'd just like clarity whether the river is running as just the consumer
client, or is actually running an embedded MQ server and consumer client.