-
Notifications
You must be signed in to change notification settings - Fork 9
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
Refactor code design #18
Comments
cc @LosD feel free to come up with a suggestion and I'll edit the issue with your ideas. |
I have a few, though some of them may not be worth the effort.
|
@LosD I'm thinking of rewriting the river [as soon as I find some time] in a better manner using Scala. Are you interested in hacking some Scala? :) |
My Scala experience is rather limited (we use it for a few tests and analysis tools at my employer), but yeah :-) On 24 January 2015 17:49:27 CET, Mihnea Dobrescu-Balaur [email protected] wrote:
|
Heads up: I've been at the ElasticSearch Core training today, and they warned me that rivers are deprecated. They will still be there in 2.0, but probably not much longer than that. Logstash is now the expected way to get data into ES, so we might not want to put too much energy into updating the river. However, I know nothing about Logstash, so I don't know if it would even be viable for importing stuff from Github. |
More info here https://www.elastic.co/blog/deprecating_rivers |
Thanks for the info! :) Will keep that in mind. |
Need
The code should be nicely structured in order to make it easy to contribute.
Deliverables
Solution
TODO
The text was updated successfully, but these errors were encountered: