Released on April 6, 2016.

New Features

Dashboard:
- Introduction of custom widgets. See Dashboard Custom Widgets API for a detailed descriptions and examples on how to use it.
Include data loader in Squirro toolbox

Improvements

Search bar alignment and buttons improved
Better http and object cache management
Generate a stable item id to improve bulk loading
Remove Save option from Search Bar widget
Remove foreground limit for significant terms widget

Bug Fixes

Fix sub items view in dashboard modal view
Set correct item creation date for bulk loading
Fix double quotes handling in facet values
Fix highlighting for proximity searches
Fix field search for language specific fields (e.g. title or body)
Use correct facets for heat-map facet value formatting

Updates

Updated Elasticsearch to version 2.2

Upgrade Instructions

As this version contains an update to a new major version of elasticsearch, it is only possible to directly upgrade from a Squirro version bigger than 2.3. If you are currently running a version smaller than 2.3., please upgrade to 2.3.1 first before you upgrade to this version. Please follow the upgrade instructions on Squirro 2.2.0 - Release Notes, Squirro 2.2.6 - Release Notes and Squirro 2.3.0 - Release Notes.

If you are using Squirro in a Box, then there are additional steps involved. In this case, please contact support.

Step 1: Prepare the upgrade

It is not possible to update to this version without a service interruption.

The upgrade will re-index your data, therefore you need at least 50% of the disk space available on your storage nodes.

THE ORDER OF THE FOLLOWING STEPS IS IMPORTANT, DO NOT SKIP ANY STEP!

Step 2: Stop squirro

On each cluster node, run:

root$ monit all stop

Step 3: Update the elasticsearch templates

On each storage node, one after the other, run:

root$ rpm -Uvh --nodeps $(repoquery --location squirro-elasticsearch-templates)

This will update the templates and re-index all indices with the new mapping v6. This may take a while.

Warning: Do not use yum update squirro-elasticsearch-templates as this tries to update elasticsearch at the same time.

Step 4: Update elasticsearch

root$ rpm -Uvh --nodeps $(repoquery --location elasticsearch)

Elasticsearch will not start as there are configuration conflicts between the two versions that need to be fixed manually:

warning: /etc/elasticsearch/elasticsearch.yml created as /etc/elasticsearch/elasticsearch.yml.rpmnew
warning: /etc/init.d/elasticsearch created as /etc/init.d/elasticsearch.rpmnew
warning: /etc/sysconfig/elasticsearch created as /etc/sysconfig/elasticsearch.rpmnew
warning: /usr/lib/systemd/system/elasticsearch.service created as /usr/lib/systemd/system/elasticsearch.service.rpmnew

Networking behaviour changed with ES2. Make sure you add the following to the /etc/elasticsearch/elasticsearch.yml file:

network.bind_host: _eth0_,127.0.0.1

network.publish_host: _eth0_

File permissions:

ensure /etc/elasticsearch/* is readable by the elastic user.
Ensure that /var/log/elasticsearch/ is readable and writeable by the elastic user.

Resolve these issues and then start elasticsearch:

root$ service elasticsearch start

Ensure elasticsearch is running before continuing. Depending on your configuration, ES might not come up until you updated a second storagenode as it requires at least one slave to be present.

Step 5: Update elasticsearch plugins and all other packages

root$ yum update

Step 6: Upgrade Cluster Nodes