-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
elasticsearch-plugin list error response #20691
Labels
Comments
I agree this feels wrong |
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this issue
Mar 13, 2017
…ible This commit catches the underlying failure when trying to list plugin information when a plugin is incompatible with the current version of elasticsearch. This could happen when elasticsearch is upgraded but old plugins still exist. With this change, all plugins will be output, instead of failing at the first out of date plugin. closes elastic#20691
rjernst
added a commit
that referenced
this issue
Mar 21, 2017
…ible (#23562) This commit catches the underlying failure when trying to list plugin information when a plugin is incompatible with the current version of elasticsearch. This could happen when elasticsearch is upgraded but old plugins still exist. With this change, all plugins will be output, instead of failing at the first out of date plugin. closes #20691
rjernst
added a commit
that referenced
this issue
Mar 21, 2017
…ible (#23562) This commit catches the underlying failure when trying to list plugin information when a plugin is incompatible with the current version of elasticsearch. This could happen when elasticsearch is upgraded but old plugins still exist. With this change, all plugins will be output, instead of failing at the first out of date plugin. closes #20691
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Running the 5.0.0 beta1;
We shouldn't generate a massive error like this.
Ideally we should just list the plugins and then highlight the incompatibility, like this;
But if not, then just having a plain text response like
Plugin [PLUGINNAME] is incompatible with Elasticsearch [VERSIONNOW]. Was designed for version [VERSIONPAST]
would be great.This is what KB does after upgrading;
At this point, I'd still need to upgrade, though it doesn't stacktrace and could have info on the incompatibilities to make things clear.
The text was updated successfully, but these errors were encountered: