Skip to content
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

Closed
ertug opened this issue Aug 4, 2014 · 3 comments
Closed

Why not use a river? #2

ertug opened this issue Aug 4, 2014 · 3 comments

Comments

@ertug
Copy link

ertug commented Aug 4, 2014

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

@sbbird
Copy link

sbbird commented Sep 12, 2014

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.
Decoupling them is not bad idea I think.

@reachkrishnaraj
Copy link
Owner

Thanks, @sbbird

reachkrishnaraj pushed a commit that referenced this issue Jun 24, 2015
Add timelimit 102 to stop ConsumerJob
@utmishra
Copy link

@sungaomengold sungaomengold mentioned this issue Jan 4, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants