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

Rivers are deprecated #67

Open
lukas-vlcek opened this issue Apr 1, 2015 · 3 comments
Open

Rivers are deprecated #67

lukas-vlcek opened this issue Apr 1, 2015 · 3 comments

Comments

@lukas-vlcek
Copy link
Member

elastic/elasticsearch#10345

@velias
Copy link
Member

velias commented Apr 1, 2015

Sad to see this. Seems we finally have to develop own native indexers runtime in Searchisko.

@unibrew
Copy link
Contributor

unibrew commented Apr 22, 2015

It's just a quick idea without thinking it through very much but why not reuse logstash? The only thing really missing from it is input plugin that would do the REST incremental calls, which shouldn't be very hard to write. We probably could leverage the existing tcp input plugin https://github.com/elastic/logstash/blob/v1.4.2/lib/logstash/inputs/tcp.rb.
Preprocessing with calling ES when needed and then saving the result into ES is all there. Especially that filters available out of the box in logstash are far more feature rich than our structured-content-tools.

@lukas-vlcek
Copy link
Member Author

Rivers going away in ES 2.0 (elastic/elasticsearch#11568)

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

3 participants