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.

Sign up for GitHub

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

Jump to bottom

Rivers are deprecated #65

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

Rivers are deprecated #65

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

Comments

@lukas-vlcek
Copy link
Member

elastic/elasticsearch#10345
@unibrew
Copy link
Contributor

unibrew commented Apr 1, 2015

But what is the alternative ?

@lukas-vlcek
Copy link
Member Author

We will run the code outside of Elasticsearch infrastructure. Deprecating of rivers is neither surprise nor tragedy. In fact we will have a chance to fix some of design issues in Searchisko.

velias added a commit that referenced this issue Apr 1, 2015
@velias
#65 - river deprecation note added to readme
1d1e3e9
@lukas-vlcek
Copy link
Member Author

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

@zp-markusp
Copy link

Any plans to address this topic in the next couple of weeks? ES 2 is coming and there is no way around...
Otherwise I would start writing an own tool for this, but then very likely in golang.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lukas-vlcek @unibrew @zp-markusp