Open peske opened 8 years ago
Same issue here - not ideal, but I just installed Elasticsearch 1.0.0, which is fine for the analyzer tool. It seems to be recognising the plugin as I wasn't getting any errors (like I was with other name patterns).
Looks like it's just a typo on my part. The URL that is used is whatever the plugin directory is called. So when the plugin is installed, it goes to "elasticsearch-inquisitor".
Another thing has came through my mind - a compatibility issue. Is the plugin compatible with ElasticSearch 2.3.3? If not you should consider changing your compatibility matrix in "readme" file - 1.0+ in my world means 1.0 and newer, thus including 2.3.3.
It should be, although I haven't tested it. I don't think any of the APIs that it uses have been affected by backwards compat breaks. But I'm not sure tbh, as this plugin has been largely dormant for a few years.
Also note: _site plugins are going to be removed in 5.0, so Inquisitor will no longer work at some point. I'd like to migrate it to a Kibana app at some point, but I just don't have a ton of free time for that atm.
For convenience, new URL that works: http://localhost:9200/_plugin/elasticsearch-inquisitor/
I'm using ElasticSearch 2.3.3 (the newest at the moment), and I've installed this plugin by following your instructions:
Then I've tried to open the site at
http://localhost:9200/_plugin/inquisitor
(again by following your instructions), and I've got nothing (404 not found).Then I've saw that the plugin directory name is different, so I've used this name and tried:
And I've got the page.
So my question is obvious - what happened? Should I specify directory name during the installation?
Another thing has came through my mind - a compatibility issue. Is the plugin compatible with ElasticSearch 2.3.3? If not you should consider changing your compatibility matrix in "readme" file - 1.0+ in my world means 1.0 and newer, thus including 2.3.3.