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

ES 1.X Support #89

Open
cidthecoatrack opened this issue Jan 31, 2018 · 4 comments
Open

ES 1.X Support #89

cidthecoatrack opened this issue Jan 31, 2018 · 4 comments
Assignees
Labels

Comments

@cidthecoatrack
Copy link

This is a question, but it has been asked in the forums and went unanswered, and there is no concrete answer anywhere. Does this plugin support reading inputs from an ES 1.X Index? The earliest mentioned version is 2.2, and when I attempt to hit a 1.X index, I get the following error: ElasticsearchIllegalArgumentException[Failed to decode scrollId]. If you explicitly don't support indexes that old, it is fine, but PLEASE specify it somewhere in the documentation. If you do, please specify how to correct this issue.

@cidthecoatrack
Copy link
Author

Update: looking through the release notes, I notice how 4.0.3 fixed the scrolling issue which broke scrolling in 1.X. However, since you can't disable scrolling (as far as I can find), it effectively breaks all of 1.X compatibility. Therefore, either there is a need to explicitly say 1.X is not supported because of scrolling, or to allow a user to disable scrolling in a request.

@andrewvc
Copy link
Contributor

andrewvc commented Feb 7, 2018

I agree, we should document this. Any support of Elasticsearch 1.x is purely accidental at this point.

@andrewvc andrewvc added the docs label Feb 7, 2018
@andrewvc andrewvc assigned andrewvc and unassigned andrewvc Feb 7, 2018
@jordansissel
Copy link
Contributor

@andrewvc agree we should document the minimum version of Elasticsearch that works (2.x?)

@jordansissel
Copy link
Contributor

jordansissel commented Feb 8, 2018

Elasticsearch 1.x is no longer developed and is unsupported. We don't test on it.

If you want Elasticsearch 1.x support, it might be best to fork this plugin and maintain 1.x support yourself.


That said, I agree with @andrewvc and @cidthecoatrack that we should document this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants