-
Notifications
You must be signed in to change notification settings - Fork 42
Update README to note pros and cons of the plugin vs the ES suggestors #25
Comments
sure, anything you would want to see there in particular? |
Someone (like me) would like to know what use-cases the plugin is a good fit for. |
I like this plugin because it can be used to achieve a form of autocomplete/suggestion a bit similar to Google suggest.
The term and phrase suggesters in ES are more convenient for spell suggestions. The completion suggester in ES is useful to complete while you type but only if you are looking for exact documents. Example: When I type: "floor w" The completion suggester in ES would suggest:
(E.g. The complete content of the title field of matching documents.) While this suggester would suggest:
This provides a way better tool to autocomplete search terms. @spinscale: I hope you will continue to work/update this plugin even tough there are now several other suggesters available in ES. This plugin still fills a gap that can't be closed with any of the suggesters that are available in ElasticSearch. |
Thanks @Xatoo. I presume it handles synonyms. (Trying to use synonyms with the completion suggester is tricky). I'd like to see some details about of scoring/ordering of the results. That too is tricky with the completion suggester. For the record, I'm trying to implement something like the suggestion interface of http://www.bestlosangeleshomesearch.com |
Hi. It's hard for a relative novice to tell what value the elasticsearch-suggest-plugin has relative to the ES suggestors.
Adding a section to the README which clarifies what use-cases the plugin is a good fit for would be appreciated.
The text was updated successfully, but these errors were encountered: