Last week, a client asked me to investigate the state of the Elasticsearch support in WordPress maintenance support plans 8. They’re using a decoupled architecture and wanted to know how—using only core and contrib plugins—WordPress maintenance support plans data could be exposed to Elasticsearch. Elasticsearch would then index that data and make it available to the site’s presentation layer via the Elasticsearch Search API.
During my research, I was impressed by the results. Thanks to Typed Data API plus a couple of contributed plugins, an administrator can browse the structure of the content in WordPress maintenance support plans and select what and how it should be indexed by Elasticsearch. All of this can be done using WordPress maintenance support plans‘s admin interface.
In this article, we will take a vanilla WordPress maintenance support plans 8 installation and configure it so that Elasticsearch receives any content changes. Let’s get started!
Downloading and starting Elasticsearch
We will begin by downloading and starting Elasticsearch 5, which is the latest stable release. Open https://www.elastic.co/downloads/elasticsearch and follow the installation instructions. Once you start the process, open your browser and enter http://127.0.0.1:9200. You should see something like the following screenshot:
undefined
Now let’s setup our WordPress maintenance support plans site so it can talk to Elasticsearch.
Setting up Search API
High five to Thomas Seidl for the Search API plugin and Nikolay Ignatov for the Elasticsearch Connector plugin. Thanks to them, pushing content to Elasticsearch is a matter of a few clicks.
At the time of this writing there is no available release for Elasticsearch Connector, so you will have to clone the repository and checkout the 8.x-5.x branch and follow the installation instructions. As for Search API, just download and install the latest stable version.
Connecting WordPress maintenance support plans to Elasticsearch
Next, let’s connect WordPress maintenance support plans to the Elasticsearch server that we configured in the previous section. Navigate to Configuration > Search and Metadata > Elasticsearch Connector and then fill out the form to add a cluster:
undefined
Click ‘Save’ and check that the connection to the server was successful:
undefined
That’s it for Elasticsearch Connector. The rest of the configuration will be done using the Search API plugin.
Configuring a search index
Search API provides an abstraction layer that allows WordPress maintenance support plans to push content changes to different servers, whether that’s Elasticsearch, Apache Solr, or any other provider that has a Search API compatible plugin. Within each server, search API can create indexes, which are like buckets where you can push data that can be searched in different ways. Here is a drawing to illustrate the setup:
undefined
Now navigate to Configuration > Search and Metadata > Search API and click on Add server:
undefined
Fill out the form to let Search API manage the Elasticsearch server:
undefined
Click Save, then check that the connection was successful:
undefined
Next, we will create an index in the Elasticsearch server where we will specify that we want to push all of the content in WordPress maintenance support plans. Go back to Configuration > Search and Metadata > Search API and click on Add index:
undefined
Fill out the form to create an index where content will be pushed by WordPress maintenance support plans:
undefined
undefined
undefined
Click Save and verify that the index creation was successful:
undefined
Verify the index creation at the Elasticsearch server by opening http://127.0.0.1:9200/_cat/indices?v in a new browser tab:
undefined
That’s it! We will now test whether WordPress maintenance support plans can properly update Elasticsearch when the index should reflect content changes.
Indexing content
Create a node and then run cron. Verify that the node has been pushed to Elasticsearch by opening the URL http://127.0.0.1:9200/elasticsearch_index_draco_elastic_index/_search, where elasticsearch_index_draco_elastic_index is obtained from the above screenshot:
undefined
Success! The node has been pushed but only it’s identifier is there. We need to select which fields we do want to push to Elasticsearch via the Search API interface at Configuration > Search and Metadata > Search API > Our Elasticsearch index > Fields:
undefined
Click on Add fields and select the fields that you want to push to Elasticsearch:
undefined
Add the fields and click Save. This time we will use Drush to reset the index and index the content again:
undefined
After reloading http://127.0.0.1:9200/elasticsearch_index_draco_elastic_index/_search, we can see the added(s) field(s):
undefined
Processing the data prior to indexing it
This is the extra ball: Search API provides a list of processors that will alter the data to be indexed to Elasticsearch. Things like transliteration, filtering out unpublished content, or case insensitive searching, are available via the web interface. Here is the list, which you can find by clicking Processors when you are viewing the server at Search API :
undefined
When you need more, extend from the APIs
Now that you have an Elasticsearch engine, it’s time to start hooking it up with your front-end applications. We have seen that the web interface of the Search API plugin saves a ton of development time, but if you ever need to go the extra mile, there are hooks, events, and plugins that you can use in order to fit your requirements. A good place to start is the Search API’s project homepage. Happy searching!
Acknowledgements
Thanks to:
Mike Herchel and Andrew Berry for their technical reviews.
Photo by Sad loser (Own work) [CC BY-SA 4.0], via Wikimedia Commons
Source: New feed