ElasticSearch
ElasticSearch integration replaces build-in MySQL FULLTEXT or regular search with ElasticSearch. This integration requires ElasticSearch server.
It can be useful for the sites with a lot of data to leverage search on another server and free MySQL from this task. Also ElasticSearch can return more relevant search results.
If you are adding this module to the site with existing content, then you need to index all existing data, it can be done from ElasticSearch module configuration page in Studio.
This module works with site search by keyword and don't work with custom search, but we'll add custom search support in the future.
-
VB I am using this presently. After some trial and tribulations it seems to be fairing pretty well. Though, more complex search capabilities would be appreciated!
Do note that the API URL in the module must be formatted as "<HTTP Protocol>://<ElasticSearch IP>:<Specified Query/Ingest Port>". You cannot have an ending / in the API URL. An example is "https://localhost:9200". Note, installing ElasticSearch on the same VM/dedicated box as UNA is a bit counter productive. It is best to turn up ElasticSearch on a dedicated VM/box. I went on and built a 4 node cluster for resiliency and performance as the UNA install grows. But, it is also ingesting server log data without a blip.
For those that are worried about IP space, you should be able to use RFC1918 space. I just happen to have a fairly large allocation of IPv6 and utilized that for back office systems. There's no issue utilizing IPv6! However, do be careful and ensure your hosts are behind firewalls. You wouldn't want these exposed anymore than necessary!