-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why not use a river? #2
Comments
To support easy hot swapping? I guess sometimes I may want to pretreat messages before pushing them to ES, I can rewrite the consumer (MessageHandler) without restarting Kafka. |
Thanks, @sbbird |
reachkrishnaraj
pushed a commit
that referenced
this issue
Jun 24, 2015
Add timelimit 102 to stop ConsumerJob
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
There is also a river for Kafka [1]. What is the advantage of using a standalone consumer?
I think adding such a comparison to README would clarify use cases.
Thank you,
Ertug
[1] https://github.com/endgameinc/elasticsearch-river-kafka
The text was updated successfully, but these errors were encountered: