Released on April 6, 2016.
Introduction of custom widgets. See Custom Widgets in the documentation for a detailed descriptions and examples on how to use it.
Search bar alignment and buttons improved
Better HTTP and object cache management
Generate a stable item identifier to improve bulk loading
Remove Save option from Search Bar widget
Remove foreground limit for significant terms widget
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
- Updated Elasticsearch to version 2.2
Fresh Installation Instructions
For a fresh installation on a single node, the number_of_shards and number_of_replicas need to be adjusted to the /etc/elasticsearch/elasticsearch.yml configuration file:
In addition for fresh installations the following four elasticsearch related permissions need to be set manually like so:
These issues will be addressed with the upcoming release 2.3.3 .
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 contact support.
This is not the latest version of Squirro. To upgrade to this version, please ensure that you point the squirro yum repository to version '2.3.2' and not to 'latest'.
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 order of the following steps is important, do not skip any step. If a step fails, do not continue before resolving the issue.
Step 2: Stop Squirro
On each cluster node, run:
Step 3: Update the Elasticsearch templates
On each storage node, one after the other, run:
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
Elasticsearch will not start as there are configuration conflicts between the two versions that need to be fixed manually:
Networking behaviour changed with Elasticsearch 2. In a multi-storagenode setup, make sure that the elasticsearch cluster network configuration is set up correctly. In a standard setup, adding the following to the
/etc/elasticsearch/elasticsearch.yml file should work:
For further help, please consult https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html
/etc/elasticsearch/*is readable by the elastic user.
- Ensure that
/var/log/elasticsearch/is readable and writable by the elastic user.
Resolve these issues.
Remove the ES plugins as they are no longer compatible (new ones will be installed by yum update):
And last, index the percolation queries that could not be migrated automatically (only required if the file /tmp/elasticsearch/squirro_v5_filter.out exists):
Step 5: Update Elasticsearch plugins and all other packages
Depending on your configuration, Elasticsearch might not come up until you updated a second storage node as it requires at least two nodes to be present.
Depending on your index size, the initial start of elasticsearch service will take a while as it migrates the index internally.
Step 6: Upgrade Cluster Nodes
On each cluster node, run:
|If you run Squirro in a multi-cluster-node environment you need to do the following additional steps on each cluster node:|
For the cluster node (or in a multi-cluster-node environment all cluster nodes), please run the following steps needed to exercise the new custom widgets extension with release 2.3.2
Then start Squirro again: