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
Add _cat/plugins endpoint #4824
Comments
personally I'd much rather have this as part of the
the |
@uboness But what if you have many plugins on the node? That would be a very long line... The |
The more I think about it the more I realize that it would make sense to separate the plugin info and the node info... Also discussed it with Boaz and the general feeling is that the es/jvm versions belong to the nodes API, and for the plugins we can have a dedicated API... (Which can potential return the mete data info as well.. Eg description) On Tue, Jan 21, 2014 at 3:02 PM, Karel Minarik notifications@github.com
|
👍 for |
I'm more for |
I think it could be nice to have a full overview of all versions (nodes, jvm and plugins). If we restrict on plugins, I can add more columns, such as:
WDYT? |
I don't think, from a user perspective, that the user wants to know information about version.. .they want to know information about nodes (and jvm/es versions are part of that info)... if they want to know versions of plugins.. .it comes from the perspective of knowing information about plugins... hence the dedicated and yeah... having a |
If we want to have a full picture of versions running in a cluster, we need to add a `_cat/plugins` endpoint. Response could look like: ```sh % curl es2:9200/_cat/plugins?v node component version type url desc es1 mapper-attachments 1.7.0 j Adds the attachment type allowing to parse difference attachment formats es1 lang-javascript 1.4.0 j JavaScript plugin allowing to add javascript scripting support es1 analysis-smartcn 1.9.0 j Smart Chinese analysis support es1 marvel 1.1.0 j/s http://localhost:9200/_plugins/marvel Elasticsearch Management & Monitoring es1 kopf 0.5.3 s http://localhost:9200/_plugins/kopf kopf - simple web administration tool for ElasticSearch es2 mapper-attachments 2.0.0.RC1 j Adds the attachment type allowing to parse difference attachment formats es2 lang-javascript 2.0.0.RC1 j JavaScript plugin allowing to add javascript scripting support es2 analysis-smartcn 2.0.0.RC1 j Smart Chinese analysis support ``` Closes elastic#4824.
Looks good! |
If we want to have a full picture of versions running in a cluster, we need to add a `_cat/plugins` endpoint. Response could look like: ```sh % curl es2:9200/_cat/plugins?v node component version type url desc es1 mapper-attachments 1.7.0 j Adds the attachment type allowing to parse difference attachment formats es1 lang-javascript 1.4.0 j JavaScript plugin allowing to add javascript scripting support es1 analysis-smartcn 1.9.0 j Smart Chinese analysis support es1 marvel 1.1.0 j/s http://localhost:9200/_plugins/marvel Elasticsearch Management & Monitoring es1 kopf 0.5.3 s http://localhost:9200/_plugins/kopf kopf - simple web administration tool for ElasticSearch es2 mapper-attachments 2.0.0.RC1 j Adds the attachment type allowing to parse difference attachment formats es2 lang-javascript 2.0.0.RC1 j JavaScript plugin allowing to add javascript scripting support es2 analysis-smartcn 2.0.0.RC1 j Smart Chinese analysis support ``` Closes #4824.
Reproducible using ES 1.1.0. `/_cat/plugins` works fine when no plugins are installed. But once a plugin is installed (eg. latest marvel), it throws an exception indicating that the resulting table constructed has 7 fields in the header row but not enough fields in the data rows to make it a valid table. ``` { "status" : 500, "error" : "ElasticsearchIllegalStateException[mismatch on number of cells 6 in a row compared to header 7]" } ``` This issue has been introduced when we removed `isolation` feature in 1.1 branch. See c34d8bd. Closes #5715
If we want to have a full picture of plugins running in a cluster, we need to add a
_cat/plugins
endpoint.Response could look like:
The text was updated successfully, but these errors were encountered: