|Search feature information|
|ElasticStore the component to establish a connection between Semantic MediaWiki and a Elasticsearch cluster.|
The ElasticStore was introduced as part of Semantic MediaWiki 3.01 to provide a powerful and scalable QueryEngine that can serve enterprise and wiki-farm users better by moving query heavy computation to an external entity (meaning separated from the main DB master/replica) known as Elasticsearch2.
ElasticStore provides a framework to replicate Semantic MediaWiki related data to an Elasticsearch cluster and enable its
QueryEngine to send
#ask requests and retrieve information from Elasticsearch (aka ES) instead of the default
The objective is to provide an interface to Elasticsearch to:
- improve structured (and allow unstructured) content searches
- extend and improve full-text query support (including sorting of results by relevancy)
- provide means for a scalability strategy by relying on the ES infrastructure
- Elasticsearch: Recommended 6.1+, Tested with 5.6.6
- Semantic MediaWiki: 3.0+
~6.0or PHP ^5.6.6
We rely on the elasticsearch php-api to communicate with Elasticsearch and are therefore independent from any other vendor or MediaWiki extension that may use ES as search backend (e.g.
It is recommended to use:
- ES 6+ due to improvements to its sparse field handling
- ES hardware with "... machine with 64 GB of RAM is the ideal sweet spot, but 32 GB and 16 GB machines are also common ..." as noted in the elasticsearch guide
- Handle property type changes without the need to rebuild the entire index itself after it is ensured that all
ChangePropagationjobs have been processed
- Inverse queries are supported (e.g.
- Property chains and paths queries are supported (e.g.
- Category and property hierarchies are supported
Before the ElasticStore (hereby Elasticsearch) can be used as drop-in replacement for the existing
QueryEngine the following settings and operations are necessary:
$GLOBALS['smwgDefaultStore'] = 'SMWElasticStore';
$GLOBALS['smwgElasticsearchEndpoints'] = [ ... ];
- Rebuild the index using
Elasticsearch is not expected to be used as data store replacement and therefore it is not assumed that ES will return all
_source fields during a request.
ElasticStore provides a customized serialization format to transform and transfer its data, an DSL interpreter (see domain language) allows for existing
#ask queries to be answered by an ES instance without changing its syntax when switching from a